Login  Register

Re: Using a display connection name fails (through NewtFactory)

Posted by Sven Gothel on Jun 13, 2013; 8:29am
URL: https://forum.jogamp.org/Using-a-display-connection-name-fails-through-NewtFactory-tp4029333p4029394.html

On 06/13/2013 10:26 AM, Sven Gothel wrote:

> On 06/13/2013 10:24 AM, gouessej [via jogamp] wrote:
>>     neothemachine wrote
>>     gouessej [via jogamp] wrote:
>>     > Maik, would it be enough for you? System.getProperty() returns a system
>>     > property, not the value of an environment variable unlike
>>     > System.getenv().get().
>>
>>     That's the point :)
>>
>>     Jogl already uses the environment variable (a bit hidden through the
>>     'null' value of X11Lib.XOpenDisplay(null). What I want is to force Jogl
>>     to use a different (custom) value instead. And the key is that it's not
>>     possible to change environment variables, but it is possible to change
>>     system properties.
>>
>> Ok but then, should we name it "DISPLAY"? Shouldn't we pick a more specific
>> name? x11.newt.display? whatever?
>
> We agreed to name it X11_DEFAULT_DISPLAY
> to avoid [future] collisions ..
While thinking about it, yes, the namespace is important,
since it is a java system property.

Better name:
  'nativewindow.x11.display.default'

- using the trusted namespace 'nativewindow.*',
  e.g. readable via PropertyAccess.

- looks nice and java'ish :)

~Sven

>
> ~Sven
>
>


--
health & wealth
mailto:[hidden email] ; http://jausoft.com
land : +49 (471) 4707742 ; fax : +49 (471) 4707741
Timezone CET: PST+9, EST+6, UTC+1


signature.asc (911 bytes) Download Attachment