| | [ Return to Bugs & Features | Roadmap 2.0 | Post Text | Post File ]
STR #1473
| Application: | FLTK Library |
|---|
| Status: | 5 - New |
|---|
| Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Unassigned |
|---|
| Summary: | fluid2 doesn't handle static class member callback functions properly |
|---|
| Version: | 2.0-current |
|---|
| Created By: | kispaljr |
|---|
| Assigned To: | Unassigned |
|---|
| Fix Version: | Unassigned |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
[ Post File ]No files
Trouble Report Comments:
[ Post Text ]
| |
| #1 | kispaljr
11:52 Oct 17, 2006 |
| If you add the name of a static class member function as the callback in fluid2 (like: ClassA::button_cb) it generates 'extern' lines for it in the header file (like: extern void ClassA::button_cb(fltk::Button*, void*)), which is syntactically wrong.
It would be nice to add a checkbox to the dialog when you set the callback to be able to indicate the fact that no extern decalration is needed for the callback function.
(and you set the necessary include files in the 'Extra code' section.) | |
| |
| #2 | engelsman
01:40 Jul 20, 2008 |
| This looks like FLTK1 STR http://www.fltk.org/str.php?L2011
so maybe something based on my patch there can be applied here. | |
[ Return to Bugs & Features | Post Text | Post File ]
|
| |
FLTK Apps 
