Re: After upgrading from JOGL1 my canvas dies when moving between monitors
Posted by Sven Gothel on Apr 19, 2013; 1:29am
URL: https://forum.jogamp.org/After-upgrading-from-JOGL1-my-canvas-dies-when-moving-between-monitors-tp4028978p4028984.html
On 04/18/2013 08:25 PM, wspear [via jogamp] wrote:
> A quick update: Digging in with some simpler examples it looks like the
> renderer by itself isn't the problem. The dispose call is coming from higher
> up in the UI stack. Unless the dispose call arrives when dragging between
> windows this issue will not occur and that only happens with my full
> application, not my little canvas-only test cases.
>
> I'm still trying to figure out what part of my UI is sending dispose on a
> monitor switch. executeDisplayChangedOnEDT in AWT's XWindowPeer class calls
> the awt.component's setGraphicsConfiguration and this is what leads to the
> dispose but all of that is fired off in its own thread and I can't tell where
> in my UI code it's coming from via the stack trace.Even though this extra lifecycle (destroy/init) triggered by a monitor switch
is not desired - a GLEventListener shall survive it.
As posted earlier, I haven't experienced such extra lifecycle in my
tests.
Hence it would be nice to know the details, and whether we really need
the extra lifecycle.
AFAIK .. we had this issue a while ago w/ some AWT implementation
and you might want to search for it in the forum/bugzilla.
~Sven
URL: https://forum.jogamp.org/After-upgrading-from-JOGL1-my-canvas-dies-when-moving-between-monitors-tp4028978p4028984.html
On 04/18/2013 08:25 PM, wspear [via jogamp] wrote:
> A quick update: Digging in with some simpler examples it looks like the
> renderer by itself isn't the problem. The dispose call is coming from higher
> up in the UI stack. Unless the dispose call arrives when dragging between
> windows this issue will not occur and that only happens with my full
> application, not my little canvas-only test cases.
>
> I'm still trying to figure out what part of my UI is sending dispose on a
> monitor switch. executeDisplayChangedOnEDT in AWT's XWindowPeer class calls
> the awt.component's setGraphicsConfiguration and this is what leads to the
> dispose but all of that is fired off in its own thread and I can't tell where
> in my UI code it's coming from via the stack trace.
is not desired - a GLEventListener shall survive it.
As posted earlier, I haven't experienced such extra lifecycle in my
tests.
Hence it would be nice to know the details, and whether we really need
the extra lifecycle.
AFAIK .. we had this issue a while ago w/ some AWT implementation
and you might want to search for it in the forum/bugzilla.
~Sven
signature.asc (911 bytes) | Free forum by Nabble | Edit this page |