| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 264.1 | never mind | AKO484::SHEPRO | NOW what'd I do? | Tue Feb 21 1989 16:04 | 6 |
| Never mind. The documentation fails to mention to make the definitions
in the DECW$LOGICAL_NAMES table.
Alan
|
| 264.2 | Taking the opportunity to pose a question | POOL::HALLYB | The smart money was on Goliath | Wed Feb 22 1989 09:52 | 8 |
| On another topic - has anybody noticed that in .0 EVERY wide line ends
with the "diamond" character, indicating overflow to the right?
I'm running character-cell NOTES. Is this a NOTES phenomenon or is it
DECterm or ... ?
John
|
| 264.3 | Probably a result of font experminents. | IAGO::SCHOELLER | Who's on first? | Wed Feb 22 1989 10:03 | 5 |
| Probably an attribute of using a wide DECterm or DECwindows NOTES configuration.
These things tend to happen when experimenting with non-default fonts.
Dick
|
| 264.4 | maybe its notes | SK8R::CRITZ | Richard -- KB4N/1 | Wed Feb 22 1989 19:44 | 5 |
| Maybe it's because note creation under DW notes is the only thing I've
seen that doesn't do automatic text wrap. It behaves like the text
widget in all other respects. I find it most annoying but haven't
tracked down how to complain about it.
|
| 264.5 | Did things change from V1 to V2? | WOOK::LEE | Wook... Like 'Book' with a 'W' | Thu Aug 03 1989 14:42 | 7 |
| Is there any reason why the DECW$Printer_Format* logicals have to be in
the DECW$LOGICAL_NAMES table? I used to be able to define them in my
process table and applications like DECW$Mail would honor them. Now it
seems that I can't put them in the process table anymore.
Wook
|
| 264.6 | V2 is the same (LNM$FILE_DEV) | R2ME2::OBRYAN | When in doubt, let the user decide. | Fri Aug 04 1989 01:40 | 12 |
|
re:.5 -< Did things change from V1 to V2? >-
> Is there any reason why the DECW$Printer_Format* logicals have to be in
> the DECW$LOGICAL_NAMES table? I used to be able to define them in my
> process table and applications like DECW$Mail would honor them. Now it
> seems that I can't put them in the process table anymore.
They should work fine in your process table. Are you running decw$mail in
a detached process or subprocess? If its a subprocess, you migth try using
the job table instead. (Also, if you're using two machines, be aware that
the logicals are examined on the client machine, not the server.)
|
| 264.7 | Restart application is the trick! | WR2FOR::LAMB_PE | Peter Lamb - FSG Santa Clara | Mon Nov 06 1989 19:05 | 16 |
|
When I upgraded from DECW V1 to V2 I decided to try print formats
for the first time... I also had difficulty getting it to work.
It doesn't seem to matter whether you define it in DECW$logical_names
or as a system/process logical. The critical thing seems to be
that you need to restart the application that you want to have use
it.
For example: To test it I had filevue running and kept doing different
logical definitions (to DECW$LOGICAL_NAMES etc) and when I tried
to print a document it always give me the entier list of ques.
However, when I finally exited Filevue and started it back up things
started to work.
Peter
|
| 264.8 | Stumped on Postscript | WR2FOR::LAMB_PE | Peter Lamb - FSG Santa Clara | Mon Nov 06 1989 19:27 | 10 |
| Hi,
I spoke too soon... This seems to work ok for TEXT etc but what
do I need to do to get it to work for POSTSCRIPT?
I tried DEFINE DECW$PRINTER_FORMAT_POSTSCRIPT "POSTSCRIPT_QUE"
but this still gives me the entire list of ques! Any ideas?
Peter
|
| 264.9 | PS not POSTSCRIPT | MELTIN::dick | Gvriel::Schoeller | Mon Nov 06 1989 19:35 | 7 |
| Try:
DEFINE DECW$PRINTER_FORMAT_PS "POSTSCRIPT_QUE"
It will work a whole lot better.
Dick
|
| 264.10 | Problem solved - use PS | WR2FOR::LAMB_PE | Peter Lamb - FSG Santa Clara | Mon Nov 06 1989 20:00 | 8 |
|
The solution seems to be to define it as follows...
DEFINE DECW$PRINTER_FORMAT_PS "POSTSCIRPT_QUE"
Does anyone know where all the various types for this are documented?
Peter
|
| 264.11 | It's in the Installation Guide | RTL::GRASS | Steve Grass | Tue Nov 07 1989 13:04 | 3 |
| See section 10.3 (table 10-4) of the VMS V5.3 Installation Guide.
steve
|