[MBS] Display problem (MBS Xojo Plugin Mailinglist archive)
|[MBS] Display problem - Louis|
|Re: [MBS] Display problem - Christian Schmitz|
|[MBS] Display problem|
|Date: 10.04.12 23:51 (Tue, 10 Apr 2012 18:51:56 -0400)|
I have this problem using Windows screen function and maybe someone here can
First, the screen function (or rather DisplayMBS class) works as it should.
It is linked to Windows screen system, so in fact, what I have is more or
less a windows undesirable feature that I'm trying to work around.
The problem I have is this. I have 3 monitors setup. Let's say I have a 15
inch that act as a control monitor that I'll call A, and two 17 inches that
I use to display a slideshow. I'll number them B and C.
Everything works fine, as long as no one unplugs a monitors or turns it
In which case, Windows notices it and reorders it's windows index.
I previous case, say I had:
System screen 0 mapped to monitor A
System screen 1 mapped to monitor B
System screen 3 mapped to monitor C
If someone closes monitor B it becomes:
System screen 0 stays mapped to monitor A
System screen 1 becomes mapped to monitor C
And it gets worse if the system monitor (index 0) is turned of by mistake.
You can see how this mixes up the whole system with ugly consequences, like
the control interface ending up in the slideshow screen.
What I'm after is a way to map my program's screens, not to Windows screens,
but rather, to the actual monitor themselves.
I probably could use the information string returned in Windows, when we
click on a monitor in the Windows monitors Control Panel, but currently, I
do not know how to get that string in RB.
Or there is maybe a more direct way to adress the monitors themselves,
bypassing Windows system entirely.
I'm open to all suggestions.
Mbsplugins_monkeybreadsoftware.info mailing list
<email address removed>
|Re: [MBS] Display problem|
|Date: 11.04.12 07:28 (Wed, 11 Apr 2012 08:28:54 +0200)|
|From: Christian Schmitz|
Am 11.04.2012 um 00:51 schrieb Louis:
> I have this problem using Windows screen function and maybe someone here can
Our WindowsMonitorMBS is newer, maybe same monitor has different index, but same handle (hMonitor)?
Could you check? In that case you could find it again in the new list of monitors based on hMonitor or the device name?