In article <3A5DC808.EA3DE467@icbt.com>,
Alain Bonnefoy <email@example.com> wrote:
PAYRE serge a écrit :
I’am trying to use nedit editor onto NTO V2.1 server with phindows and I
have the following problem :
When i start the editor on my computer in a phindows windows, the editor
appears on another terminal
we are working on win 95 an win nt.
(I have the same problem with DDD debugger)
Could you help me ?
If I’m not wrong, nedit is an X application. So, it requires xphoton. The
problem is that xphoton is only launched (now) on the first started photon
session (it will be fixed soon).
Correct, ddd and nedit are X apps.
Quick answer, start your own Xphoton.
In phindows, in a pterm,
$ Xphoton :1 -once &
$ export DISPLAY=127.1:1.0
$ gtwm &
any other X applications started (with DISPLAY=127.1:1.0)
will connect to this Xphoton…
If someone is already running an Xphoton as (X)display 1 substitute
Few months ago Garry Turcote gave me some scripts to start xphoton correctly
but I didn’t succeed to use these. I think I didn’t understand everything
I’ll try to explain
The default/standard/current (pick a term) Photon startup, runs
Xphoton as (X)display 0 and sets your environment so X applications
can connect to (X)display 0 (ie. export DISPLAY=127.1:0.0)
If you start another Photon session on the same machine using
phindows for example, it goes through the same startup procedure.
Xphoton is already running, attached to the first Photon session, so
the second Xphoton fails to start. But your environment is still
set to connect to (X)display 0, so any X applications you start
will display in the first Photon session.
Garry Turcotte (R&D)
QNX Software Systems, Ltd.