Re: Using a display connection name fails (through NewtFactory)
Posted by
Sven Gothel on
Jun 12, 2013; 3:24pm
URL: https://forum.jogamp.org/Using-a-display-connection-name-fails-through-NewtFactory-tp4029333p4029384.html
On 06/12/2013 05:22 PM, Sven Gothel wrote:
> On 06/12/2013 04:50 PM, neothemachine [via jogamp] wrote:
>> Can you ensure in your testing environment that a specific unit test
>> doesn't have the DISPLAY environment variable set? Otherwise, I'll leave
>> the unit test out for now and just submit the single-line fix as pull
>> request.
>
> Yes, we can fiddle w/ the env vars when launching a unit test.
>
>>
>> Thanks for your support :)
>
> Good that this case(1) is solved.
>
> (1) No DISPLAY env. variable set, hence no default X server available.
> Injecting custom default X server via Java system property 'DISPLAY'.
>
> .. while (2) was always working:
>
> (2) Having a default X server being set via DISPLAY env variable.
> Using the default X server, _as_well_ as other X server,
> while naming the display connection, i.e. 'host2:22.1' via
> AbstractGraphicsDevice, .. etc.
>
> Maybe we should document this somewhere ?
>
> Are you willing to add a wiki page for it and link it
> to the JOGL tutorial/howto section ?
> If yes - I create an account for you, pls PM me - sgothel at jausoft dot com.
>
.. and the git pull request pls .. thank you!
> ~Sven
>
>> Maik
>
--
health & wealth
mailto:
[hidden email] ;
http://jausoft.comland : +49 (471) 4707742 ; fax : +49 (471) 4707741
Timezone CET: PST+9, EST+6, UTC+1