| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #301
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 4 - High, e.g. key functionality not working |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | FLUID |
|---|
| Summary: | fluid declaration block guards not exported to header files (fix attached) |
|---|
| Version: | 1.1.4 |
|---|
| Created By: | daniel.barrero.polymtl |
|---|
| Assigned To: | mike |
|---|
| Fix Version: | 1.1.5rc1 |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
Trouble Report Comments:
| |
| #1 | daniel.barrero.polymtl
09:56 Mar 01, 2004 |
| There is a problem with the code generation in fluid 1.4.4, when defining a declaration block (#ifndef) there's no option to set it public or not, As a result if i put inside the ifdef a public declaration the public declaration (i.e. an #include) goes to the .h file but not the block guards.. they only appear on the .cxx file causing problems later at compilation time.
I've made a modified version of fluid that solves the problem, and guarantees that if the guards are private the declarations inside are not exported to the .h file even if declared public (although the private declarations for a public blok stay private)... i've modified the codeblock_panel definition on the function_panel.fl Fl_type.h Fl_Function_Type.cxx files) and modified the code saving and generation functions of the declaration block to take into account the public property..
| |
| |
| #2 | mike
19:41 Mar 10, 2004 |
| Thanks, applied to CVS for 1.1.5. | |
[ Return to Bugs & Features ]
|
| |
