TheJim01
16th February 2010, 20:44
I use the tutorial here (http://thelins.se/learnqt/2009/06/an-embedded-linux-development-setup/) to set up my environment to cross-compile applications for the qvfb environment.
I also set up a custom skin, and mapped four buttons to what should be the keys "1", "2", "3", and "4".
[SkinFile]
Up=arp_up.png
Down=arp_down.png
Screen=9 13 480 800
Cursor=finger.png 0 0
Areas=4
HasMouseHover=false
"Up" 0x0031 60 866 125 930
"Next" 0x0032 166 866 231 930
"Down" 0x0033 270 866 335 930
"Mode" 0x0034 375 866 440 930
I then made a simple GUI application with a Plain Text Area. I compiled this using my qvfb setup, and can launch the application so it runs in the qvfb buffer.
It works great, but I'm having an issue trying to use the skin's buttons. I would have expected the buttons to emulate (and override) the keyboard at this point, but when I set the focus to the Plain Text Area and click the buttons, nothing happens (I expect it to output the numbers assigned).
Were my assumptions incorrect? Did I miss a flag (or set an incorrect flag) when compiling my qvfb environment and/or application?
Also, the Internet seems to be barren of examples of this scenario--does anyone know of any examples showing how to capture the qvfb buttons and use them? I realize it will be different on real hardware, but a software prototype will suit my needs perfectly, for now.
I also set up a custom skin, and mapped four buttons to what should be the keys "1", "2", "3", and "4".
[SkinFile]
Up=arp_up.png
Down=arp_down.png
Screen=9 13 480 800
Cursor=finger.png 0 0
Areas=4
HasMouseHover=false
"Up" 0x0031 60 866 125 930
"Next" 0x0032 166 866 231 930
"Down" 0x0033 270 866 335 930
"Mode" 0x0034 375 866 440 930
I then made a simple GUI application with a Plain Text Area. I compiled this using my qvfb setup, and can launch the application so it runs in the qvfb buffer.
It works great, but I'm having an issue trying to use the skin's buttons. I would have expected the buttons to emulate (and override) the keyboard at this point, but when I set the focus to the Plain Text Area and click the buttons, nothing happens (I expect it to output the numbers assigned).
Were my assumptions incorrect? Did I miss a flag (or set an incorrect flag) when compiling my qvfb environment and/or application?
Also, the Internet seems to be barren of examples of this scenario--does anyone know of any examples showing how to capture the qvfb buttons and use them? I realize it will be different on real hardware, but a software prototype will suit my needs perfectly, for now.