Christian Convey wrote:
> When I sorted out the multithreading issues we were having with FLTK, I
> believed that MY_LockableOutput was no longer needed, and all instances of it
> could be replaced with Fl_Output. What I didn't realize is that the class
> MY_LockableOutput also has another important method:
> int MY_LockableOutput::handle(int) { return 0; }
> which I'm told will permit arrow key presses to propagate to the menu. So
> restoring that approach is my next task.
If this turns out to be your real and only problem, then you may
not even need to derive your own class (MY_LockableOutput) and
write a handle() method. Deactivating your widgets may be enough:
my_output->deactivate(); // this grays the widget out
my_output->set_output(); // deactivates w/o graying out
http://www.fltk.org/doc-1.1/Fl_Widget.html#Fl_Widget.deactivate
http://www.fltk.org/doc-1.1/Fl_Widget.html#Fl_Widget.set_output
Albrecht
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
