> performing a fl_read_image *after* fl_end_offscreen() simply > causes an ugly segmentation fault. > This is awkward, the offscreen buffer still should exist, I'd > expect fl_delete_offscreen( offscreen ) to completely remove > the offscreen (so obviously any interaction after the delete > is doomed to fail). > why should I be forced to copy the offscreen while it still > is the active context? I'd rather be free to copy it whenever > I want, as long as the offscreen doesn't get deallocated.
fl_read_image only handles the current context, so if you want to read from the offscreen, it has to be current. That's just the way it is, I'm sorry. A lot of what you are doing is really non-standard, so to some extent you are stretching the implementation beyond its intended purpose. > Another small details: I deallocate the pixmap by delete[], > but is it allocated by new[]? otherwise this could be another > source of instability. > I hope you all work with the new/delete operator guys ... The pixmap used by fl_read_image? If you read the docs, you will find the answer to that question. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
