Christian Lippka wrote:
Hi David,
I hope I find some time soon to draft an API for a component that can
be used to handle multi display support for different platforms.
I'm not sure yet if your approch to use an integer to identify a
display is sufficient. If on X it is also a string who identifies a
display we should use a string as a handle. Sure the component must
then also provide a user interface string for each registered monitor.
In a simple case this could just result in strings like "Display X" or
"Primary Display", "Secondary Display" etc.
Would be nice if we can have the same string representation on windows
as in the display settings dialog, f.e. "Sun 22 HDTV on ATI X800 XXL".
Yes this makes sense.
So it seems what we need is an enumerator that can list the available
displays, giving you the display name etc, and probably a number we can
use internally to specify the display (e.g. when passing to
ShowFullScreen as Phillip suggested).
I think ImplSalCalcFullScreenSize ist a nice place to make vcl multi
display aware for desktop sized (fullscreen) windows. But I think this
is mainly Philips area of expertise.
For the dialog patch I think we must support a textual representation
of the display, not only the number.
Yes given the above enumerator this would work.
Something we should discuss is if we need support for displays that are
not part of the desktop. For OOo this would currently not work on
windows as there is no free direct x canvas implementation. But even
if there was a canvas implementation that could theoreticaly work
with a non desktop display, for some features we still need the
posibility to overlay windows on the presentation. F.e. plugins or
controls.
Thorsten, ist it safe to assume that we never will support such
displays?
I don't know much about displays that aren't part of the desktop so I'll
leave that for now :-)
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
