Re: [fltk.general] Fl_Scroll calling draw() on bar drag event, but not drawing

2011-01-25 Thread james
Got it for sure! Haha. I used an offscreen buffer and a redraw() and it works like a charm now. Thanks a lot guys! ___ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk

Re: [fltk.general] Fl_Scroll calling draw() on bar drag event, but not drawing

2011-01-24 Thread Matthias Melcher
On 24.01.2011, at 06:45, james wrote: Right on, that fixed it! Thanks a lot! As an explanation, I'm making a an overview of a collection of heightmaps (for 3d landscapes) and well the optimizations of the Fl_Scroll are kind of glitchy when scrolling quickly. I noticed this when I was

Re: [fltk.general] Fl_Scroll calling draw() on bar drag event, but not drawing

2011-01-24 Thread MacArthur, Ian (SELEX GALILEO, UK)
Okay, I totally lied there. The fl_push_no_clip will just take over the window and not update ever no matter where I scroll to. Ah, right. Well in that case, *cough* fl_offscreen *cough*... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14

Re: [fltk.general] Fl_Scroll calling draw() on bar drag event, but not drawing

2011-01-23 Thread Ian MacArthur
james wrote: Heya! So I have a Fl_Box inside of a Fl_Scroll. I'm taking over the draw() of my box, and when I scroll around by clicking and dragging on the nobs, my draw function can only draw on the newly exposed pixels. It simply blits the pixels that are still on the screen over to their

Re: [fltk.general] Fl_Scroll calling draw() on bar drag event, but not drawing

2011-01-23 Thread Matthias Melcher
On 23.01.2011, at 05:05, james wrote: Heya! So I have a Fl_Box inside of a Fl_Scroll. I'm taking over the draw() of my box, and when I scroll around by clicking and dragging on the nobs, my draw function can only draw on the newly exposed pixels. It simply blits the pixels that are still

Re: [fltk.general] Fl_Scroll calling draw() on bar drag event, but not drawing

2011-01-23 Thread Ian MacArthur
Matthias Melcher wrote: On 23.01.2011, at 05:05, james wrote: How can I eliminate this buffer that exists? Well, the draw() function as it is called by Fl_Scroll is optimized so it doesn't need to redraw the entire area, but simply moves pixels around that are still on the screen. This

Re: [fltk.general] Fl_Scroll calling draw() on bar drag event, but not drawing

2011-01-23 Thread james
On 23.01.2011, at 05:05, james wrote: Heya! So I have a Fl_Box inside of a Fl_Scroll. I'm taking over the draw() of my box, and when I scroll around by = clicking and dragging on the nobs, my draw function can only draw on the = newly exposed pixels. It simply blits the pixels that are

Re: [fltk.general] Fl_Scroll calling draw() on bar drag event, but not drawing

2011-01-23 Thread james
On 23.01.2011, at 05:05, james wrote: Heya! So I have a Fl_Box inside of a Fl_Scroll. I'm taking over the draw() of my box, and when I scroll around by = clicking and dragging on the nobs, my draw function can only draw on the = newly exposed pixels. It simply blits the pixels

[fltk.general] Fl_Scroll calling draw() on bar drag event, but not drawing

2011-01-22 Thread james
Heya! So I have a Fl_Box inside of a Fl_Scroll. I'm taking over the draw() of my box, and when I scroll around by clicking and dragging on the nobs, my draw function can only draw on the newly exposed pixels. It simply blits the pixels that are still on the screen over to their new position.