Re: Using a display connection name fails (through NewtFactory)
Posted by Sven Gothel on Jun 09, 2013; 11:23pm
URL: https://forum.jogamp.org/Using-a-display-connection-name-fails-through-NewtFactory-tp4029333p4029363.html
On 06/09/2013 11:10 PM, neothemachine [via jogamp] wrote:
>> I don't know whether that works w/ JOGL, i.e. not a DISPLAY
>> specified for JOGL (see above).
>
> Nope, I already tried that. I don't remember the exact error, but it was
> missing the display connection.
>
>> IMHO it is also possible to specify the DISPLAY env. var from Java itself,
>> i.e. before you initialize JOGL .. (e.g. via GLProfile.initSingleton()).
>
> Unfortunately no, otherwise I would have just done that. One can use
> dirty hacks but those will break for sure:
> http://stackoverflow.com/a/7201825/60982
>
> Maybe you mixed this up with the system properties accessible by
> 'System.[get|set]Property(..)'.Though we have something like 'System.setenv("DISPLAY")' :)
At least from jenkins, as well as w/ glassfish you can set
environment vars .. well.
>
>> All in all .. it's not a bug - but some 'misunderstanding'.
>>
>> So .. let me know what way you prefer and how we can assist.
>
> Well, thinking about it, I guess the most convenient (for JOGL as well
> as for me) fall-back would be if JOGL would check the
> System.getProperty("DISPLAY") value if the System.getenv("DISPLAY")
> value was not specified. I know that such change is much to ask, after
> all it is really a corner case, but on the other side I guess it
> requires very little change in the code base and won't affect anything
> else in any way.
>
> What do you think?Ok .. pls file a bugreport as an enhancement,
then we can follow on this.
Pls. add your feature request in the bug report,
your description above is very well.
Even though you don't feel confident participating
in the implementation .. maybe you still like to try.
However, it's not a 1st prio feature .. but it will be done eventually.
Thank you.
Cheers, Sven
>
> Cheers
> Maik
URL: https://forum.jogamp.org/Using-a-display-connection-name-fails-through-NewtFactory-tp4029333p4029363.html
On 06/09/2013 11:10 PM, neothemachine [via jogamp] wrote:
>> I don't know whether that works w/ JOGL, i.e. not a DISPLAY
>> specified for JOGL (see above).
>
> Nope, I already tried that. I don't remember the exact error, but it was
> missing the display connection.
>
>> IMHO it is also possible to specify the DISPLAY env. var from Java itself,
>> i.e. before you initialize JOGL .. (e.g. via GLProfile.initSingleton()).
>
> Unfortunately no, otherwise I would have just done that. One can use
> dirty hacks but those will break for sure:
> http://stackoverflow.com/a/7201825/60982
>
> Maybe you mixed this up with the system properties accessible by
> 'System.[get|set]Property(..)'.
At least from jenkins, as well as w/ glassfish you can set
environment vars .. well.
>
>> All in all .. it's not a bug - but some 'misunderstanding'.
>>
>> So .. let me know what way you prefer and how we can assist.
>
> Well, thinking about it, I guess the most convenient (for JOGL as well
> as for me) fall-back would be if JOGL would check the
> System.getProperty("DISPLAY") value if the System.getenv("DISPLAY")
> value was not specified. I know that such change is much to ask, after
> all it is really a corner case, but on the other side I guess it
> requires very little change in the code base and won't affect anything
> else in any way.
>
> What do you think?
then we can follow on this.
Pls. add your feature request in the bug report,
your description above is very well.
Even though you don't feel confident participating
in the implementation .. maybe you still like to try.
However, it's not a 1st prio feature .. but it will be done eventually.
Thank you.
Cheers, Sven
>
> Cheers
> Maik
signature.asc (911 bytes) | Free forum by Nabble | Edit this page |