| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 373.1 | bugs me too | CADSYS::YOST | | Fri Mar 10 1989 09:29 | 9 |
|
I find this annoying too. It is not configurable from the session
manager. I think the session manager just utilizes its own 'best fit'
for the size of terminal window(s). There may be an undocumented parameter
for sys$library:decw$terminal.dat or decw$terminal.uil (note, we don't get
the source *.uil , just the compiled *.uid) or something else.
clay
|
| 373.2 | | VWSENG::KLEINSORGE | Toys 'R' Us | Fri Mar 10 1989 09:47 | 8 |
|
I don't get the impression that any "best fit" is done, since I
consistantly get terminal windows created partially offscreen
(hardly a best fit). It looks like the windows always start at
a specific location and each additional one is slightly lower and
to the right of the previous one.
|
| 373.3 | You can't do it from the session manager | PRNSYS::LOMICKAJ | Jeff Lomicka | Fri Mar 10 1989 12:18 | 7 |
| Start them from DECW$LOGIN.COM using the command:
$ CHILD/X=x-coord/Y=y-coord/IMAGE=SYS$SYSTEM:LOGINOUT.EXE/NOPASS/DETACH
Get CHILD from PRNSYS::RELEASED_TOOLS:[CHILD]*.*, read CHILD.TXT.
|
| 373.4 | There's no increment resource either | REVEAL::LEE | Wook... Like 'Book' with a 'W' | Fri Mar 10 1989 16:53 | 12 |
| I asked this question in the DECterm conference and was told that the x and y
increments were hard coded at 10 pixels each if my memory isn't fried.
Now I use Child and my own setup files which I can edit if I want to change
anything rather than have to edit my login everytime.
BTW: CHILD doesn't seem to be translating my process-level logicals that I pass
as part of the setup file specification. I ended up parsing it myself using the
f$parse lexical with the noconceal argument.
Wook
|
| 373.5 | CHILD/SETUP parsing context | PRNSYS::LOMICKAJ | Jeff Lomicka | Mon Mar 13 1989 10:47 | 8 |
| The set-up file name in CHILD is parsed in the context of the DECTerm
process.
I suppose I should SYS$PARSE this before I send it on to DECTerm, but
for now, your workaround is the correct procedure.
|
| 373.6 | Resources will work, but not as expected | OIWS20::BRYSON | | Mon Mar 13 1989 12:35 | 69 |
| You can set the X and Y position of your DECterms through resources, but not
as you would think. It is true that the increment for the offsets are set
at 30 and that the default x and y position is 100,100; however, the following
resources will affect these if used in selected ways:
DECW$TERMINAL.x: <some x pixel location>
DECW$TERMINAL.y: <some y pixel location>
Now for the kludgy part!
You could create a special customization file for EACH of your expected
DECterm terminals. To make it easy to use, call them
SYS$LOGIN:DECW$TERMINAL_<unique name>.DAT
In this file, place the above lines with the desired positions. Select
the "Use Last Saved Settings From..." under Customize menu. Select the
appropriate customization file. WARNING: this will probably reset
some parameters, so the customization file may need to have more resources
to specify the characteristics you desire. The terminal will move to
the requested location.
A little bit nicer change is to the way that DECterms are created on the
display which does not involve going to each DECterm. These modification are
to the file SYS$LOGIN:DECW$TERMINAL_DEFAULT.DAT. I use 0 here in the
examples but you can specify whatever position you like.
1. All DECterms to appear on top of one another (same as ultrix)
DECW$TERMINAL.x: 0
DECW$TERMINAL.y: 0
Not extremely nice, but...
2. DECterms appear vertically when created.
DECW$TERMINAL.x: 0
Looks like
-------------------
| DECterm 1 |
-------------------
| DECterm 2 |
-------------------
| DECterm 3 |
| |
-------------------
3. DECterms appear horizontally when created.
DECW$TERMINAL.y: 0
Looks like
----------------------------
| | | | DECterm 4 |
| | | | |
----------------------------
Not quite as usable, but...
Remember, the increment CANNOT be changed, so in 2 and 3 the offset is always
30 pixels.
David
|