Updates:
Status: WontFix
Comment #5 on issue 245 by benoit.m...@gmail.com: Wrong behaviour in
desktop.w and screen.w on dual head?
http://code.google.com/p/gambas/issues/detail?id=245
You should use the Rect class and its Union() method. It's easier with it.
--
Comment #4 on issue 245 by kokok...@gmail.com: Wrong behaviour in desktop.w
and screen.w on dual head?
http://code.google.com/p/gambas/issues/detail?id=245
I ended up in using the following code, it seems to mimic the previous
desktop.h and desktop.w behaviour.
However, it could fail in some
Comment #3 on issue 245 by kokok...@gmail.com: Wrong behaviour in desktop.w
and screen.w on dual head?
http://code.google.com/p/gambas/issues/detail?id=245
Oh wow, i totally missed the screens class, i think i can manage to get the
same info as before with it, but i'm pretty sure the generic
Comment #2 on issue 245 by benoit.m...@gmail.com: Wrong behaviour in
desktop.w and screen.w on dual head?
http://code.google.com/p/gambas/issues/detail?id=245
I think now you should use the Screen and Screens classes. Screens.Count
gives you the number of screens, and Screens[] returns a Scre
Updates:
Status: NeedsInfo
Labels: -Version Version-TRUNK
Comment #1 on issue 245 by benoit.m...@gmail.com: Wrong behaviour in
desktop.w and screen.w on dual head?
http://code.google.com/p/gambas/issues/detail?id=245
Do you know if there is a way for a guy that has only one scre
Status: New
Owner:
Labels: Version Type-Bug Priority-Medium OpSys-Any Dist-Any Arch-Any
Desktop-Any GUI-Any
New issue 245 by kokok...@gmail.com: Wrong behaviour in desktop.w and
screen.w on dual head?
http://code.google.com/p/gambas/issues/detail?id=245
I've a dual head configuration, de
