inmarket Posted April 12, 2015 Report Share Posted April 12, 2015 A GWIN virtual keyboard widget has been added. Link to comment Share on other sites More sharing options...
woodstock Posted November 10, 2015 Report Share Posted November 10, 2015 I'm struggling to get this feature working. I've borrowed the relevant code from the modules/gwin/textedit/ demo and switched on the required features in gfxconf.h, however I get the following linker error:undefined reference to `GKEYBOARDVMT_OnlyOne'I have noticed for touch devices, a VMT structure (i.e. GMouseVMT) is statically initialised in the LLD file for the particular touch device and this is how the VMT list is populated (I think), however such a driver or static initialisation does not exist for the Virtual Keyboard (as far as I know...).I must be missing something incredibly obvious here. :?Thanks in advance! Link to comment Share on other sites More sharing options...
inmarket Posted November 11, 2015 Author Report Share Posted November 11, 2015 Please turn off GINPUT_NEED_KEYBOARD. That setting is required for a hardware keyboard only. That is what it is complaining about - the lack of a linked hardware keyboard driver. Link to comment Share on other sites More sharing options...
Joel Bodenmann Posted November 14, 2015 Report Share Posted November 14, 2015 Just curious... did this fix the problem you were having, woodstock?~ Tectu Link to comment Share on other sites More sharing options...
woodstock Posted November 15, 2015 Report Share Posted November 15, 2015 Yes, turning off GINPUT_NEED_KEYBOARD fixed this problem – silly me :oops:.[EDIT] just remembered that I had to make a small fix to get it working. I'll send a pull request shortly. Link to comment Share on other sites More sharing options...
Joel Bodenmann Posted November 15, 2015 Report Share Posted November 15, 2015 Thank you for sending the pull request, we appreciate your contributions a lot!Btw, as mentioned in an earlier post we would prefer the .patch file being attached to an explaining post here in the forum as it is easier for us to maintain it this way. Sadly bitbucket doesn't allow to download the patch file from a pull-request so it is rather cumbersome for us to try and verify the changes on our local testing repository before merging. Also, while the pull requests are usually totally fine there are some minor or additional changes required in other parts of the µGFX library to ensure proper compatibility across all features and platforms. In those cases we first have to merge the pull request and then modify the required things.This are also the reasons why there are many "declined" pull requests on the bitbucket site: Nearly all of them got merged but manually due to the issues described here.We definitely appreciate all your contributions!~ Tectu Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now