T.R | Title | User | Personal Name | Date | Lines |
---|
2838.1 | | WKRP::LENNIG | Dave (N8JCX), SWS, Cincinnati | Thu May 31 1990 01:01 | 5 |
| Forgot to mention...
I'm running 5.3-2
Dave
|
2838.2 | | WKRP::LENNIG | Dave (N8JCX), SWS, Cincinnati | Fri Jun 01 1990 10:42 | 4 |
| Am I asking this in the wrong conference, or is it just to dumb a
question?
Dave
|
2838.3 | | DECWIN::FISHER | Prune Juice: A Warrior's Drink! | Fri Jun 01 1990 10:49 | 3 |
| Probably as good a conference as any; maybe no one knows.
Burns
|
2838.4 | Try fileview conference | SCAM::DIAL | | Fri Jun 01 1990 10:50 | 5 |
| It would seem to be a reasonable question, perhaps there aren't many
fileview users here. You can customize DECterm, but I don't know about
fileview's terminal emulator. Try the fileview conference.
Barry
|
2838.5 | BULOVA::FILEVIEW | UTRTSC::CAHILL | Got no bags&baggage to slow me down | Fri Jun 01 1990 11:15 | 1 |
|
|
2838.6 | | HANNAH::MESSENGER | Bob Messenger | Mon Jun 04 1990 15:05 | 27 |
| Re: .0
Do you want to disable cursor blink for the DCL Command window *and* for
DECterm, or just for the DCL Command window?
Both Fileview (for its DCL Command windiw) and DECterm use the DECterm
widget, which has a class name of DECterm. To turn off cursor blink for
all your DECterm widgets, put this resource definition into your
decw$user_defaults:decw$xdefaults.dat file:
*DECterm.cursorBlinkEnable: off
I'm not sure how to turn it off just for the DCL Command window. It
depends on the widget hierarchy that Fileview uses. To turn it off in
DECterm you could say:
DECW$TERMINAL.main.terminal.cursorBlinkEnable: off
One way to turn it off for everything *but* DECterm is:
*DECterm.cursorBlinkEnable: off
DECW$TERMINAL.main.terminal.cursorBlinkEnable: on
The second definition takes precedence over the first because it doesn't
contain any wild cards.
-- Bob
|
2838.7 | Ah hah, a beginning... | WKRP::LENNIG | Dave (N8JCX), SWS, Cincinnati | Thu Jun 07 1990 18:27 | 25 |
| re: .-1
Thanks for the info. Here's the situation.
A VAXstation, 9600 baud asynch decnet link, a remote Fileview.
After some experimenting, my overall perception is that the "DCL
Command" utility is more responsive across the link than the "DECterm"
application. (I understand this can probably be attributed to
differences between how Fileview and the DECterm controller manage the
pseudo-terminal). The only thing that was troublesome with the "DCL
Command" window, was the packet exchanges for the cursor blink.
This prompted my query.
Your response brings up a more interesting question though. (Please
keep in mind I've just recently started using/hacking DECwindows).
Can I interpret your note to say there is a way to turn off *all* cursor
blinking for my entire remote Fileview? If so, How?
I'll start experimenting shortly, but the otehr question with .-1 is,
since I'm dealing with a remote Fileview, do these "resources" (right
word?) go on the workstation, or the remote system?
Thanks,
Dave
|
2838.8 | | HANNAH::MESSENGER | Bob Messenger | Fri Jun 08 1990 11:06 | 16 |
| Re: .7
> Can I interpret your note to say there is a way to turn off *all* cursor
> blinking for my entire remote Fileview? If so, How?
No, I was just talking about the DECterm widget. Maybe one of the Fileview
people can tell you how to disable blinking of non-DECterm cursors.
> I'll start experimenting shortly, but the otehr question with .-1 is,
> since I'm dealing with a remote Fileview, do these "resources" (right
> word?) go on the workstation, or the remote system?
They go on the system running Fileview (i.e. on the client rather than on
the server).
-- Bob
|