> >> Hah, I got it!
> >
> > Oh yes - good stuff: and that ties in with "Consul" the
> OP's observation
> > in
> >
> > http://www.fltk.org/newsgroups.php?gfltk.development+v:12583
> >
> > that setting num_screens to zero "fixes" the issue, too...
>
> Yes, maybe, as a side effect, but you knew that since you wrote
> "fixes" ;-)
OK - I stared at the num_screens thing for a bit and realised we were
initialising it to a non-zero value by calling
num_screens = GetSystemMetrics(SM_CMONITORS);
And then subsequently incrementing num_screens even further in the
screen_cb(...) function, thereby totally messing up the indexing into
the screens[] array...
Fltk-1.1 used to reset num_screens = 0 before starting to iterate over
the screen_cb(...) function so it got this right.
Anyway, I've pushed in a correction for this which seems to work fine in
my tests, and added a comment about how we might also recover the
work-area along with the screen area. (But not any actual work on that
as such...)
It's a start and I believe fixes the initial problem, anyway.
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-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
