> > What FLTK functions are you using to create the image in memory? > I can only think of 'fl_read_image()'
This is exactly what I am doing, except I am using a stripped and modified version of fl_read_image() because I need both color and b/w versions of the image for the printer. I also looked at your explonations for malloc/free issues and I have some more information. I noticed that the memory decreases every time a DIFFERENT page is displayed in Fl_Help_View, i.e. if I display the same page again, the memory is not decreased even if I 'delete' and 'new' Fl_Help_View in between. It seems that there is some kind of history effect going on but I know that the Fl_Help_View stores only links and not the pages themselves. Therefore I believe this is somehow related to the heap allocation algorithm but I cannot explain how it remembers to reallocate memory for already viewed pages and use more memory for 'new' pages. Anyone can explain this? My printing problem is probably caused by the same phenomenon so I will not pursue it further until this can be resolved. Beacuse, I have an embedded system with limited memory and no virtual memory, I cannot sustain this kind of behaviour for too long. Any suggestions? Martin _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
