How to choose the primary screen with NEWT?

Hi

Some people use several monitors at the same time and the default Screen instance used by NEWT is a 2-monitor wide one. How can I solve this problem? How can I make the difference between 2-monitor wide Screen instances and single monitor wide Screen instances? Can I call gelAllScreens() very early to get all existing screens?

On 06/30/2012 04:04 PM, gouessej [via jogamp] wrote:
> Hi
>
> Some people use several monitors at the same time and the default Screen
> instance used by NEWT is a 2-monitor wide one. How can I solve this problem?
> How can I make the difference between 2-monitor wide Screen instances and
> single monitor wide Screen instances? Can I call gelAllScreens() very early to
> get all existing screens?

Right, I remember this situation back then when we
discussed and multi-monitor mode and fixed it by
allowing negative window coordinates.

We know (as you describe it) all current usual systems merge
all monitors and present them as 1 screen device.

Back then I started adding support of querying
the attached monitor/display devices so we can expose this information.

For X11 the patch utilizes xrandr version 13
to query the monitor/display layout. This work is at ~50%
For Windows and OSX this still would need to be done.

With given monitor layout one would be able to match coordinates
to a monitor.

I interrupted this task (code on my stash) due to other issues.

Maybe we file a bug report (enhancement) for it and after RC10/11
we may have a chance to squeeze that in.

Cheers, Sven

PS: Good reading your WebGL writeup. I even didn't accept
the claim that JavaScript/WebGL is not a plugin.

BTW .. maybe after your blog post you can post a link to it
here in jogamp [general] in case it's related. I often do this,
allowing a subsequent discussion of it - even though people rarely use
this opportunity.

Hi

At first, I have to write a bug report about a broken option in Google Chrome affecting Java Web Start / NetX. Then, I will write a bug report about your suggestion of enhancement.

P.S: I will put a link into my blog post as soon as possible, it's a good idea.

The first report is here:
https://code.google.com/p/chromium/issues/detail?id=135363

Done:
https://jogamp.org/bugzilla/show_bug.cgi?id=600

On 07/01/2012 07:38 PM, gouessej [via jogamp] wrote:
> Done:
> https://jogamp.org/bugzilla/show_bug.cgi?id=600
thx

KUDOS - bug number SIX-HUNDRED - 6 0 0

:)

~Sven