> I am useing clipping with FLTK 1.1.7 on Debian but > occassionally it stalls for a few seconds and I get these > messages on the console: > > fl_push_clip: clip stack overflow! > fl_pop_clip: clip stack underflow! > > What is going on? I only have one clipping region on the stack.
I don't think I've ever seen that - how did you manage it? One thought: You are not calling draw() directly in your code, are you? > How robust is the clipping? Can I draw anywhere and expect > the clipping to take care of it? Should be able to - I'm pretty sure I had code that used to do that (it rendered a data map that was much, much larger than the visible window...) and the clipping seemed to do the right thing. It was wasteful of cpu ticks though, so I reworked my code to only draw a section of the map covering the "viewport" - still needed clipping though. 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
