Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!sequoia!memqa!qfhca81
From: qfhca81@memqa.uucp (Henry Melton)
Newsgroups: comp.windows.x
Subject: Re: DECWindows Multi-screen problem under eXodus 2.0
Message-ID: <4645@memqa.uucp>
Date: 18 Jul 90 09:26:20 GMT
References: <4562@memqa.uucp> <10456@odin.corp.sgi.com>
Organization: Memory R&QA, Motorola SPD
Lines: 46

In article <10456@odin.corp.sgi.com>, mikey@eukanuba.wpd.sgi.com (Mike Yang) writes:
> In article <4562@memqa.uucp>, qfhca81@memqa.uucp writes:
> |> My problem is that DECWindows does not allow me to start applications
> on the 
> |> 0.1 window.  The Session Manager/Customize/Screen number window
> implies that I
> |> can either set the screen on which an application can run, or ask that I be
> |> prompted for the screen number when I start an application.  While I can set
> |> screen 1 to be used either as default or interactively, The
> application always
> |> comes up running on screen 0.
> 
> I'll assume that you're running a recent version of DECwindows and
> give you a solution for that setup.  I don't know how to make the
> session manager prompt you for the screen number when you start an
> application.
> 

My current VMS version is 5.3-1 and whatever version of DECwindows comes with
that.  When the Session manager runs on a display that has more than one screen
defined, there is an additional option under the Customize menu that allows
you to define which screen to screenprint and which screen to run applications
on, as well as a checkbox for determining the screen at runtime via a
little dialog box.  This does not work.  If I rely on this, the application
always starts on screen 0.


> However, if you always want a given application to start up on a given
> screen (you seem to), you can make this happen.  Use the "Customize"
> menu to alter the definitions of your applications so that they have a
> "-display :.0" or a "-display :.1" in them.  This should force them to
> appear on the screen of choice.

I have had no luck with this.  All I get is an error message 'Can't open
Display.' from the application.  Even a fully spelled out display address 
fails, but this could be the application?

What DOES work is to use the DCL command SET DISPLAY/SCREEN=1 before running
the application.  So I have found a workaround.  I just wish the Session
Manager would work the way it was designed to.

-- 
Henry Melton
{fast}  qfhca81@memrqa.sps.mot.com 
{slow}  qfhca81@memqa   ..!cs.utexas.edu!execu!sequoia!memqa!qfhca81
{home}  henry@hutto     ..!emx.utexas.edu!hutto!henry