| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2593.1 | We had more transports than symbol conventions; that's why we made the ws device | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Tue Apr 10 1990 13:03 | 10 |
| It can't. You need to create a display device. Ditto for LOCAL, btw.
Is it that you need to find it from a program without benefit of DCL? How
is the other program getting the wkst name that it passes you? Perhaps there
is a way for IT to get/create the WS device? The WS device gets created
automatically in a lot of places: For example, if you log in the session mgr,
you will have a WS in DECW$DISPLAY. I think the DW Terminal s/w should also
be donig it if you logged in from the terminal.
Burns
|
| 2593.2 | More on this... | STKHLM::DSUNDSTROM | Dan Sundstr�m ACT Stockholm | Tue Apr 10 1990 15:46 | 23 |
| What we have is a multithreaded program that runs detached. It gets via
a mailbox a string in the form "nodexx::0.0" and just makes an
XOpenDisplay(...) on the string. The program that writes into the
mailbox has a defined displaydevice(set display/create/node=nodexx::0)
and just makes an XOpenDisplay() and a DisplayString(dpy) -> mailbox.
When you do a set display/create/node=LAT_08002bxxyyzz/trans=lat and
puts that into the mailbox with DisplayString it givs you
LAT_08002bxxyyzz::0.0 as the string. XOpenDisplay on that does not do
what I want it to. Two possibilities;
1 The way in .1: do a getenv on decw$display to get the wsa-device and
pass that through the mailbox. This gives another problem; If you are
not sure if the writing process is there when you read the mailbox and
try to use the WSA-device it might not exist, unless you create it with
/exec but then it will never disapear... Hmmm Any thoughts ??
2 From the reading program you, when you see a LAT..., create the
device with lat transport... I dont know how to do that, does anyone
have any suggestions ??
Thanks /Dan Sundstr�m ACT Stockholm.
|
| 2593.3 | Can WS device be used instead ? | KAL::BJERKEHOLT | Bo Bjerkeholt, TPSG, SWAS, @GOO | Tue Apr 10 1990 16:00 | 13 |
|
We have a login program that is started from a command file who
do set display/cre.... .The login program picks up the node name
after XOpenDisplay("") with a DisplayString(dpy) . After that it
sends to the other application in a mailbox which works fine for
DECnet transports.
The application that receives the mailbox is multithreaded and
handles several displays ,thats why it wont use DCL and set
display.
Can the WS device be used to open the display instead ?
regards,
Bo
|
| 2593.4 | | STAR::ORGOVAN | Vince Orgovan | Tue Apr 10 1990 19:38 | 3 |
| RE: .3 Can WS device be used instead ?
Yes, XOpenDisplay accepts WS devices.
|
| 2593.5 | | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Wed Apr 11 1990 13:48 | 9 |
| Aha. Yes, XDisplayString (actually XOpenDisplay which stores the string
for XDisplayString in the first place) is broken. You can't always use it
to open another display, which is what it is there for. This is fixed in
VMS V5.4 (I think *not* in T5.4, though).
It sounds like you are using the right technique. If you can possibly hold
off for V5.4, don't make any hacks to work around the problem!
Burns
|
| 2593.6 | Don't try to parse XDisplayString! | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Wed Apr 11 1990 13:50 | 3 |
| re .-1: Caution all ye who try to parse the string coming from XDisplayString!
Burns
|