| | [ Return to Bugs & Features | SVN ⇄ GIT ]
STR #2177
| Application: | FLTK Library |
|---|
| Status: | 2 - Closed w/o Resolution |
|---|
| Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | Fl::add_handler() additional data parameter |
|---|
| Version: | 1.4-feature |
|---|
| Created By: | sanel.z |
|---|
| Assigned To: | AlbrechtS |
|---|
| Fix Version: | Will Not Fix |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | sanel.z
04:05 Mar 22, 2009 |
| It would be nice if Fl::add_handler() could have additional, void* parameter, so objects does not has to be "globalized", to be used inside handler function.
Also, it would allow per-window parameters when multiple windows are used in the same application. | |
| |
| #2 | AlbrechtS
17:55 Jan 15, 2023 |
| This is not possible or useful. From the FLTK library view there is only an event that is sent when the registered handler function is called. The processing of event calls (if you registered an event handler)
your_handler(int e);
where 'e' is the event that is to be processed. There is no further context available.
If you would want to have events of one window *sent* to one handler and events of another window sent to another handler function then this would be a completely different issue and this can't be solved with the current event processing model in FLTK.
However, if you want to discuss how your request could be implemented (and why you think that you want it), then fltk.coredev would be the right place to discuss such new features.
https://groups.google.com/g/fltkcoredev
Thanks for your understanding. STR closed. | |
[ Return to Bugs & Features ]
|
| |
