| [ Return to Bugs & Features | Roadmap 2.0 | Post Text | Post File ]
STR #1350
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 problem with image inlining |
Version: | 2.0-current |
Created By: | Reimar |
Assigned To: | Unassigned |
Fix Version: | Unassigned |
Update Notification: | |
Trouble Report Files:
[ Post File ]
Trouble Report Comments:
[ Post Text ]
|
#1 | Reimar 03:36 Jul 12, 2006 |
| I'm using fluid2 from FLTK 2.0.x Weekly Snapshot, r5253 under windoze.
Inlining images in Fluid2 seems to produce incorrect code. The data-lines of the image is placed inside the *cpp-code, but the image-variable is not further used for initialistion.
Example: Here's an extract from the *.cpp:
----------------------------------------------------- // generated by Fast Light User Interface Designer (fluid) version 2.1000
#include "Test.hpp"
#include <fltk/SharedImage.h> static const unsigned char datas_TestImage[14454] = { 66,77,118,56,0,0,0,0,0,0,54,0,0,0,40,0,0,0,80,0,0,0,60,0,0,0,1,0,24,0,0,0, 0,0 [...] 138,107,155,138,143,181,169,158,196,184,147,190,177,147,188, 176,120,183,167};
fltk::Window* make_window() { fltk::Window* w; {fltk::Window* o = new fltk::Window(118, 84); w = o; o->begin(); {fltk::Group* o = new fltk::Group(3, 7, 96, 75); o->image(fltk::SharedImage::get("C:\FluidTest/TestImage.bmp")); o->box(fltk::UP_BOX); } o->end(); o->resizable(o); } return w; }
-----------------------------------------------------
So the defined Byte array 'datas_TestImage' is not further used in the code. Am I wrong?
Greetings, Reimar
PS: What sense has the menu-item: "Set images root directory" in fluid2? I can not figure out any effects. PSS: Is it possible to define local paths (under windows)? | |
[ Return to Bugs & Features | Post Text | Post File ]
|
| |