jogamp › jogl

Regression of alwaysOnTopBug

Classic

List

Threaded

18 messages Options

Mike

Regression of alwaysOnTopBug

Hey guys,

There appears to be a regression of bug 570: https://jogamp.org/bugzilla/show_bug.cgi?id=570.

The bug is that Alt-tab doesnt work in fullscreen mode even though i explicitly set alwaysOnTop(false).

I am running version 2.1.2 of Jogamp, however I noticed this regression at least six months ago.

Thanks,
Mike

Sven Gothel

Re: Regression of alwaysOnTopBug

Administrator

On 12/01/2013 04:50 PM, Mike [via jogamp] wrote:

> Hey guys,
>
> There appears to be a regression of bug 570:
> https://jogamp.org/bugzilla/show_bug.cgi?id=570.
>
> The bug is that Alt-tab doesnt work in fullscreen mode even though i
> explicitly set alwaysOnTop(false).
>
> I am running version 2.1.2 of Jogamp, however I noticed this regression at
> least six months ago.

We have to allow the Windowmanager (WM) to take away the focus
from the fullscreen window.
Otherwise we would steal the whole desktop.

So you are saying that you cannot ALT-TAB (switch application/focus)
to another application window ?

Which platform ?
Which JOGL version ?

~Sven

>
> Thanks,
> Mike

signature.asc (911 bytes) Download Attachment

Sven Gothel

Re: Regression of alwaysOnTopBug

Administrator

In reply to this post by Mike

On 12/01/2013 07:21 PM, Sven Gothel wrote:

> On 12/01/2013 04:50 PM, Mike [via jogamp] wrote:
>> Hey guys,
>>
>> There appears to be a regression of bug 570:
>> https://jogamp.org/bugzilla/show_bug.cgi?id=570.
>>
>> The bug is that Alt-tab doesnt work in fullscreen mode even though i
>> explicitly set alwaysOnTop(false).
>>
>> I am running version 2.1.2 of Jogamp, however I noticed this regression at
>> least six months ago.
>
> We have to allow the Windowmanager (WM) to take away the focus
> from the fullscreen window.
> Otherwise we would steal the whole desktop.
>
> So you are saying that you cannot ALT-TAB (switch application/focus)
> to another application window ?
>
> Which platform ?
> Which JOGL version ?

I have tested w/ latest JOGL on X11/GNU/Linux
and Windows7.

With default settings, i.e. alwaysontop (atop) disabled,
it works as expected here, i.e.:
- ALT-TAB triggers WM dialog, switching between apps.
- ALT-TAB can actually switch to other apps.

However, with enabled atop:
- ALT-TAB triggers WM dialog, switching between apps.
- ALT-TAB does _not_ switch to other apps.

I consider this a serious issue, since we shall not steal
the desktop in fullscreen mode.
Hence - I will file a bug-report that we need to disable atop
in fullscreen mode.

~Sven

>
> ~Sven

signature.asc (911 bytes) Download Attachment

Sven Gothel

Re: Regression of alwaysOnTopBug

Administrator

In reply to this post by Mike

On 12/01/2013 10:27 PM, Sven Gothel wrote:

>
> I have tested w/ latest JOGL on X11/GNU/Linux
> and Windows7.
>
> With default settings, i.e. alwaysontop (atop) disabled,
> it works as expected here, i.e.:
> - ALT-TAB triggers WM dialog, switching between apps.
> - ALT-TAB can actually switch to other apps.
>
> However, with enabled atop:
> - ALT-TAB triggers WM dialog, switching between apps.
> - ALT-TAB does _not_ switch to other apps.
>
> I consider this a serious issue, since we shall not steal
> the desktop in fullscreen mode.
> Hence - I will file a bug-report that we need to disable atop
> in fullscreen mode.

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

>
> ~Sven

signature.asc (911 bytes) Download Attachment

Mike

Re: Regression of alwaysOnTopBug

Im running Jogl 2.1.2, on Windows 7.

In fullscreen with atop disabled i am unable to switch to other applications. When I press alt-tab my mouse cursor changes to the default windows one, but I still see my jogl app in fullscreen, and am unable to switch to any other windows. The function isAlwaysOnTop() returns false for me while I am testing this so I am sure it is disabled.

During your tests with atop disabled you were able to successfully alt-tab out of fullscreen mode?

Sven Gothel

Re: Regression of alwaysOnTopBug

Administrator

On 12/01/2013 11:09 PM, Mike [via jogamp] wrote:

> Im running Jogl 2.1.2, on Windows 7.
>
> In fullscreen with atop disabled i am unable to switch to other applications.
> When I press alt-tab my mouse cursor changes to the default windows one, but I
> still see my jogl app in fullscreen, and am unable to switch to any other
> windows. The function isAlwaysOnTop() returns false for me while I am testing
> this so I am sure it is disabled.
>
> During your tests with atop disabled you were able to successfully alt-tab out
> of fullscreen mode?

Yes. This is what surprises me :-/

ALT-TAB gives me the 'app selection pop-up window' and I can select another
application.
Releasing ALT-TAB moves the selected application 'on top'.

Please test w/ latest RC - thank you.

+++

> I consider this a serious issue, since we shall not steal
> the desktop in fullscreen mode.
> Hence - I will file a bug-report that we need to disable atop
> in fullscreen mode.

Bug 914 <https://jogamp.org/bugzilla/show_bug.cgi?id=914> is fixed now,
i.e. disabling atop when in fullscreen mode.

(Not your issue)

signature.asc (911 bytes) Download Attachment

Mike

Re: Regression of alwaysOnTopBug

I just tested it with the latest nightly build and am having the same problem. I should probably mention that I am using the NEWT GLWindow.

Ill keep fiddling around and see if i can narrow down the problem.

Mike

Re: Regression of alwaysOnTopBug

Strange, I just tried it on my other Windows 7 machine and it works fine... That PC has an Radeon HD 5870. The PC i'm having the problem with is my laptop with an Intel HD Graphics 3000. Maybe some weird driver problem, or just some windows bug?

Sven Gothel

Re: Regression of alwaysOnTopBug

Administrator

In reply to this post by Mike

On 12/02/2013 12:10 AM, Mike [via jogamp] wrote:
> I just tested it with the latest nightly build and am having the same problem.
> I should probably mention that I am using the NEWT GLWindow.
>
Of course.
I also tested w/ latest RC:
<http://jogamp.org/deployment/archive/master/gluegen_752-joal_503-jogl_1162-jocl_883-signed/jogl-applet-runner-newt-gears-normal-napplet.html>

(Notice the key actions: 'a' and 'f')

Works good here (NVidia).

> Ill keep fiddling around and see if i can narrow down the problem.

Thank you.

~Sven

signature.asc (911 bytes) Download Attachment

Sven Gothel

Re: Regression of alwaysOnTopBug

Administrator

In reply to this post by Mike

On 12/02/2013 12:33 AM, Mike [via jogamp] wrote:
> Strange, I just tried it on my other Windows 7 machine and it works fine...
> That PC has an Radeon HD 5870.

I tested w/ NVidia Windows7, so both NV and AMD are fine.

> The PC i'm having the problem with is my laptop
> with an Intel HD Graphics 3000. Maybe some weird driver problem, or just some
> windows bug?

Dunno, but will try w/ a windows box and Intel ..

Our code however strictly allows it.

~Sven

signature.asc (911 bytes) Download Attachment

Sven Gothel

Re: Regression of alwaysOnTopBug

Administrator

In reply to this post by Mike

On 12/02/2013 02:30 AM, Sven Gothel wrote:

> On 12/02/2013 12:33 AM, Mike [via jogamp] wrote:
>> Strange, I just tried it on my other Windows 7 machine and it works fine...
>> That PC has an Radeon HD 5870.
>
> I tested w/ NVidia Windows7, so both NV and AMD are fine.
>
>> The PC i'm having the problem with is my laptop
>> with an Intel HD Graphics 3000. Maybe some weird driver problem, or just some
>> windows bug?
>
> Dunno, but will try w/ a windows box and Intel ..

Reproduced on a laptop running Windows 7
using an Intel HD 4000.

This machine was last updated 2013-08-30
and I currently run a Windows update on said machine ..

Will file a bug report.

>
> Our code however strictly allows it.
>
> ~Sven
>

signature.asc (911 bytes) Download Attachment

Sven Gothel

Re: Regression of alwaysOnTopBug

Administrator

In reply to this post by Mike

On 12/02/2013 05:52 AM, Sven Gothel wrote:

> On 12/02/2013 02:30 AM, Sven Gothel wrote:
>> On 12/02/2013 12:33 AM, Mike [via jogamp] wrote:
>>> Strange, I just tried it on my other Windows 7 machine and it works fine...
>>> That PC has an Radeon HD 5870.
>>
>> I tested w/ NVidia Windows7, so both NV and AMD are fine.
>>
>>> The PC i'm having the problem with is my laptop
>>> with an Intel HD Graphics 3000. Maybe some weird driver problem, or just some
>>> windows bug?
>>
>> Dunno, but will try w/ a windows box and Intel ..
>
> Reproduced on a laptop running Windows 7
> using an Intel HD 4000.
>
> This machine was last updated 2013-08-30
> and I currently run a Windows update on said machine ..
>
> Will file a bug report.

<https://jogamp.org/bugzilla/show_bug.cgi?id=916>

Thank you for reporting this issue!

~Sven

signature.asc (911 bytes) Download Attachment

Sven Gothel

Re: Regression of alwaysOnTopBug

Administrator

In reply to this post by Mike

On 12/02/2013 05:57 AM, Sven Gothel wrote:
>
> <https://jogamp.org/bugzilla/show_bug.cgi?id=916>
>
> Thank you for reporting this issue!
>

Solved:
<https://jogamp.org/bugzilla/show_bug.cgi?id=916#c3>
<http://jogamp.org/git/?p=jogl.git;a=commit;h=354b0b370bbfd14743267a9466f5e91e4d218a42>

~Sven

signature.asc (911 bytes) Download Attachment

gouessej

Re: Regression of alwaysOnTopBug

Administrator

Sven Gothel wrote

Solved:
<https://jogamp.org/bugzilla/show_bug.cgi?id=916#c3>
<http://jogamp.org/git/?p=jogl.git;a=commit;h=354b0b370bbfd14743267a9466f5e91e4d218a42>

Good job. I didn't imagine that an Intel GPU would cause such problems.

Julien Gouesse | Personal blog | Website

Mike

Re: Regression of alwaysOnTopBug

Hey guys, this bug seems to have regressed again. Although now I can reproduce the problem on my Intel HD 3000 card, as well as a Radeon 7800 and a Gforce GTX 970

gouessej

Re: Regression of alwaysOnTopBug

Administrator

Which version of JOGL do you use?

Julien Gouesse | Personal blog | Website

Mike

Re: Regression of alwaysOnTopBug

Woops that was a vital piece of information I left out! I'm using 2.2.4. I don't think the regression is new to 2.2.4, I noticed it somewhere in 2.1.*

gouessej

Re: Regression of alwaysOnTopBug

Administrator

Please indicate exactly in which version this regression appeared, it will help a lot to find which change(s) caused it.

Julien Gouesse | Personal blog | Website