| [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #634
Application: | FLTK Library |
Status: | 1 - Closed w/Resolution |
Priority: | 3 - Moderate, e.g. unable to compile the software |
Scope: | 3 - Applies to all machines and operating systems |
Subsystem: | Core Library |
Summary: | fl_event() reports wrong evnt type |
Version: | 1.1.2 |
Created By: | mark.t |
Assigned To: | mike |
Fix Version: | 1.1.7 |
Update Notification: | |
Trouble Report Files:
Trouble Report Comments:
|
#1 | mark.t 06:08 Nov 29, 2004 |
| Over-ride the handle() method in Fl_Window to get access to more events. This function's argument (the event type) occassionally differs from what Fl::event() returns. This is confusing. How can one know which to use? It also muddies the code as you can't just use Fl::event() uniformly everywhere.
comment from Matthias: Yes, you are correct. There are quite a lot of instances in the code where the handle() argument and the Fl::event() variable differ. This happens when events are sent directly to widgets instead of going through the dispatcher.
What Fl::event() gives you is the original event that caused some action. I guess that can be seen as a bug. Could you please file an STR on the FLTK website? ----------------------------- My original post in the "general" section of the newsgroup has a very short program source attached which demonstrates this.
| |
|
#2 | mike 19:13 Dec 02, 2004 |
| Please test the attached patch and let me know if it doesn't fix the problem... | |
|
#3 | mike 19:13 Dec 02, 2004 |
| Fixed in CVS - the anonymous CVS repository will be updated at midnight PST. | |
[ Return to Bugs & Features ]
|
| |