> > > I have about a dozen buttons which will be used to change=20 > > menus/options these are read through an FPGA device, I have a=20 > > driver working that reads the FPGA on a timer and then wakes=20 > > the user space app on a epoll when a button has been=20 > > pressed/released. This all works fine but I need to generate=20 > > events for fltk. > > Hmm, OK - well, I guess there are two options here, which I imagine you > already know: > - either tweak the fltk core to insert the key presses directly > - or hook Xtest to poke values into the X11 layer >
I wasn't sure which way to go but thanks for the advice. > Either can work, though I actually might favour Xtest, FWIW. > > I guess we are talking about buttons surrounding the screen, and you > draw labels/buttons beside the physical buttons, like on an ATM or etc.? That is exactly what I'm doing. > > That said, small OEM displays with resistive touch screen overlays are > surprisingly affordable now, even in small numbers, so I'd certainly > consider going that way rather than having physical buttons and > decoding/debouncing them (physical buttons add an awful lot more h/w to > assemble/support and are a lot less flexible in use.) > And it looks cool, too. > The touch screen input just appears like a mouse click, so is easy for > the s/w to cope with. > We considered a touch screen but it was decided that physical buttons would be better suited. > > I've also tried fltk 2.0 and I now have text working, so I=20 > > will be going with that I think. > > Ah. That's interesting. > Which version of fltk2? > Is it one that's been "tweaked" for nanoX or is it stock from the fltk > tarballs? > If it is stock, then I wonder what it is doing that is different from > fltk-1.3? > I just downloaded the latest source and tweaked it a little to compile, but not much. The text works but the other bits I had working tabs, images etc... now don't. > Did you try fltk-1.1.10 BTW? > If fltk2 works, fltk-1.1.x may do so also, as IIRC the internal font > handling is similar. > Fltk-1.3 is later than either 1.1 or 2.x, and has more stuff (e.g. the > virtual device layer etc) going on under the covers that might be > implicated in font handling issues... > (Note that fltk2 was never really released as it never reached a state > that was considered stable enough for long enough! If you use it, you > may find some problems, though it mainly works well.) > > I thought v2.0 was the latest and therefore the best but with that info I may go back to 1.3 and try and get the text working again. > > SELEX Galileo Ltd > Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS= > 14 3EL > A company registered in England & Wales. Company no. 02426132 > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ******************************************************************** > Thanks for all your info/pointers/advice. Cheers Stuart. _______________________________________________ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
