| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3408.1 | | DDIF::KROBINSON | Icon do windows | Mon Oct 01 1990 11:02 | 3 |
| No it's not intentional. What version are you running? Just to cover
all the bases, are you quite sure you hit the "apply" or "OK" button?
|
| 3408.2 | alternate way... | GSRC::WEST | SCARY : A programmer with a screwdriver. | Mon Oct 01 1990 15:14 | 14 |
| RE:.-2
In some cases this is true...
What you want to do is select/set everything, then SAVE CURRENT SETTINGS
from the 'Customize' menu. After saving then just RESTORE SAVED SETTINGS
from the same menu.
The actual text may vary since I'm not on a workstation at this time to
verify, but this will give you the effect of logging off and then back
on.
-=> Jim <=-
|
| 3408.3 | Haven't got v5.4 up yet -- perhaps it's fixed there? | PEACHS::MITCHAM | Andy in Alpharetta (near Atlanta) | Mon Oct 01 1990 16:04 | 16 |
| I'm running VMS v5.3-1. Yes, I am certain that I pressed both <Apply> and
<Ok> (though <Ok> should be all that is necessary, correct?).
This started as a customer call. It seemed so elementary yet, when I tried
it, it didn't work as I thought it would. I also did as mentioned in 3408.2
-- that is, I made the change, did Save Current Settings, then Use Last Saved
Settings and the change had not taken effect. It wasn't until I'd logged off
and back on that I found the change had taken. This was the only workaround
that we could offer the customer.
If any of you have a version where this change does occur dynamically, I'd
appreciate hearing from you, however, I'd suggest trying this -first- as I
made myself look awful silly trying to demonstrate to one of the other guys
here how to make this work...
-Andy
|
| 3408.4 | Me too | SWTHOM::TISSERAND | Jean-Marc TISSERAND TSC FRANCE | Wed Oct 03 1990 14:00 | 4 |
| Hi Andy, I have the same problem too, running vms v5.4 session manager on a
remote vt1200 server.
Jean-Marc.
|
| 3408.5 | It happens in VMS v5.4 also... | PEACHS::MITCHAM | Andy in Alpharetta (near Atlanta) | Wed Oct 03 1990 16:37 | 16 |
| After delving a more, I have found that the DECW$PRINTSCREEN.TMP file is
created in the correct format (ie. the format last selected) -- it's just
that the "Print Format" displayed in the "Queue Options" menu isn't correct.
For example, if Postscript is the default print format and you change to
Sixel output format, the next printscreen output -will- be in sixel format.
However, when the Queue Options menu comes up, Postscript is still the listed
print format.
This shouldn't be a problem unless printer logicals are defined (ie.
DECW$PRINTER_FORMAT_PS or DECW$PRINTER_FORMAT_ANSI2) which could inhibit
appropriate print queues from being selected.
Looks like it's time for an SPR...
-Andy
|