| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 915.1 | | 29067::BUTTERWORTH | Gun Control is a steady hand. | Wed Aug 09 1995 17:17 | 38 |
| In the first place, none of these things are bugs.
> He has got the following problems with V1.5A:
> .)CNTRL_W (refresh) doesn't work
I'm assuming that you mean the Monitor interface. To prevent broadcasts
from goofing up the screen, broadcaast is turned off. Note the next
screen and previous screen keys will scroll you forward and back if you
want to review some console data.
> .)There is no possibility to define keys like in VCS. Only 4
The Monitor is not TPU based like it was in VCS which is one reason why
it's faster and uses less memory. You will have to ask for a request for
enhancement. Send mail to Rae Collier the product manager @
MUZICK::COLLIER. One possible alternative you might consider is the
use of scripting. If you type a command in the monitor that is not part
of it's command set, the code will look for a file named
CONSOLE$command-you-typed.SCRIPT
This file may contain any monitor commands that you wish. So if your
customer had some keys defined to do VCS monitor commands you can move
those into scripts and while you still can't just press a key you can
at least enter in a simple command that will do several tasks.
> .)only 80/132 char can be set as width/VCS is free choseable.
You will also have to request an enhancement.
I would also inform your customer that VCS is basically retired and
there will be no more development or bug fixes.
Regards,
Dan
|
| 915.2 | I don't understand Point 1 (CNTRL_W) | 49312::VNABRW::KARTNER_M | This is the road to hell | Thu Aug 10 1995 05:33 | 8 |
| Hi!
Thank you for your response. I understand all points except the first
one. (CNTRL_W)
The Monitor gets messed after several NEW,... commands. There is no way
clearing this problem by CNTRL_W (seems to do nothing)
thanks
Michael
|
| 915.3 | | 29067::BUTTERWORTH | Gun Control is a steady hand. | Fri Aug 11 1995 13:57 | 12 |
| Okay,
Now I understand your problem. Indeed ctrl-w doesn't do anything as
the code was never programmed to respond to it. The real problem is
Monitor goofing up after several previous/new commands.
You are running 1.6 with the ECO correct? I can't remember and I forgot
to look at the previous replies. The point is, I can't make Monitor
goof up the screen on my test system even if I hold the NEXT or
PREVIOUS keys down and let them autorepeat.
REgards,
Dan
|
| 915.4 | Will user defineable function KEYs ever return ? | 49312::VNABRW::KARTNER_M | This is the road to hell | Wed Aug 30 1995 08:11 | 7 |
| Hi!
Will user defineable function KEYs ever return ?
Many customers like this functionallity.
thanks
Michael
|