> > Might be worth trying with non-zero dimensions, just to see if that
> > makes any different here...
> >
> > e.g. try; MyWin() : T(5,5,90,90) {}
> >
>
> Works fine.
>
>
> A modified Fl_Double_Window.cxx works for me :
>
> in void Fl_Double_Window::flush(int eraseoverlay) {
>
> line 345-348 or near, I had a check on W() and H()
>
>
> #if defined(USE_X11) || defined(WIN32)
> myi->other_xid = ( w() && h() ? fl_create_offscreen(w(),
> h()) : 0 );
> clear_damage(FL_DAMAGE_ALL);
> #elif defined(__APPLE_QUARTZ__)
Hmm, I fear that will cause more problems than it solves...
"myi->other_xid" is subsequently used in several places without always
checking to see if it is NULL or not, so I worry that this will throw
other issues.
I think it would be better if we contrived to ensure that the offscreen
(which is used to simulate double-buffering) was never created with zero
size, which is why I suggested we try setting MyWin to a nonzero value
in my earlier post.
Creating 0 sized windows is a Bad Thing, in general. Does the tile demo
do that? I'm not at all familiar with the way in which the Fl_Tile logic
works...
I assume, from the codepath, that your X-server is not reporting that it
can support XDBE, and that is why you are seeing this problem.
I guess that these days, most testing happens on servers that do claim
to support XDBE so we go down the alternate codepath and never hit this
issue?
SELEX Galileo Ltd
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