| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 213.1 | Some comments | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Tue Mar 15 1994 21:17 | 45 |
| Dave,
> 1. Connecting from the $ prompt to a system which is for some
> reason unreachable causes a screen display problem. I don't know
> precisely why it's unreachable in this particular case - that's
> what I'm working on 8?) - but it's reported as 'Console
> inactive.'
>
> Basically the effect is that the reverse status line is wiped out
> apart from the 'Console inactive' message and on a VT the Command
> prompt is overwritten.
Are you running the latest kit which was just released? This has been a
problem in the past but it is getting better with every release.
Are you using 24 row DECterms?
> 2. <CTRL/Z> doesn't work to exit from the Command: prompt. This is
> a fairly standard shortcut to the EXIT command under VMS. (I'm
> guessing that you're u*x people - something someone said in an
> earlier note... If not - apologies, I'm teaching granny to suck
> eggs again. 8?)
This is a good point, but it's not up to me. Phil, any chance we can
squeeze this one in?
> 3. From the C3 interface connecting to a console produces two
> 'acknowledge' buttons which seems excessive! If said console is
> inactive we get a window with the 'Console inactive' message and
> the 'Command:' prompt. Typing 'CONNECT' again causes the window
> to disappear with no explanation...
I haven't seen it happen with 2 acknowledge buttons. Do you think the
acknowledge popup window is excessive? I can take it out very easily.
I thought that some users with slow systems might get impatient with
the time it takes to popup up a connect/monitor window and keep trying
repeatidly, thus causing further delays. The message box just has a 5
second timer and self cancels after that time. Others have also
commented about it and it's sounding like it might be wise to remove
it. I could look into changing the cursor to a watch for 5 seconds.
Dave
|
| 213.2 | Clarification | THEFT::DAVE | Dave Lunn. | Tue Mar 15 1994 22:22 | 21 |
|
>Are you running the latest kit which was just released? This has been a
>problem in the past but it is getting better with every release.
Yes - latest kit released a few days ago. VMS version T6.1-5Y3.
>Are you using 24 row DECterms?
Yes again - in fact right now I'm on a VT220...
>I haven't seen it happen with 2 acknowledge buttons. Do you think the
>acknowledge popup window is excessive? I can take it out very easily.
I'm sure I saw two popups... I'll double-check in the morning. *My*
preference FWIW is for watches over popups! Whichever you decide on
couldn't you disable the connect option while there is a connect in
progress to stop us shooting ourselves in the foot?
Cheers,
Dave.
|
| 213.3 | | OPG::PHILIP | And through the square window... | Wed Mar 16 1994 09:22 | 19 |
|
If you can wait a few seconds whilst I get these eggs out of
my mouth, I'll answer your questions ;-)
Point 1 we have seen before and thought we had fixed, we will
take another look at it.
Point 2 will be implemented for the SSB kit, isnt it about time
you VMS (ooops sorry OpenVMS) people got real and did things the
right way (Phew how did I manage to say that without choking ;-)
Point 3 well that down to Dave (Dave - another person who prefers
the watch cursor!!)
Keep these bugs/suggestions coming, it all helps to improve the
final quality of the product.
Cheers,
Phil
|
| 213.4 | 8?) | THEFT::DAVE | Dave Lunn. | Wed Mar 16 1994 09:56 | 21 |
| > If you can wait a few seconds whilst I get these eggs out of
> my mouth, I'll answer your questions ;-)
Funny, I use a keyboard to answer notes 8?)
> Point 1 we have seen before and thought we had fixed, we will
> take another look at it.
It grieves me to say it, but I can generate a number of screen handling
problems... do you want more details?
> Point 2 will be implemented for the SSB kit, isnt it about time
> you VMS (ooops sorry OpenVMS) people got real and did things the
> right way (Phew how did I manage to say that without choking ;-)
Now we could have an interesting discussion on the 'right way' of doing things
but I'll refrain from scrambling down that rat-hole. But I have to say I'm
surprised you didn't throw in a sneaky <CTRL/D> for the exit - hey we might
even have got used to the idea 8?)
Dave.
|
| 213.5 | | OPG::PHILIP | And through the square window... | Wed Mar 16 1994 10:49 | 24 |
| >> Point 1 we have seen before and thought we had fixed, we will
>> take another look at it.
>>
>>It grieves me to say it, but I can generate a number of screen handling
>>problems... do you want more details?
It grieves me too, but we need to fix them, so, yes, we want to know
about them all please.
>> Point 2 will be implemented for the SSB kit, isnt it about time
>> you VMS (ooops sorry OpenVMS) people got real and did things the
>> right way (Phew how did I manage to say that without choking ;-)
>>
>>Now we could have an interesting discussion on the 'right way' of doing things
>>but I'll refrain from scrambling down that rat-hole. But I have to say I'm
>>surprised you didn't throw in a sneaky <CTRL/D> for the exit - hey we might
>>even have got used to the idea 8?)
Now there is an excellent idea!! In fact we could change it so that
control-z backgrounds your job and places you at the DCL prompt in
a sub-process ;-)
Cheers,
Phil
|
| 213.6 | msg box eliminated | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Wed Mar 16 1994 14:57 | 5 |
| Phil, Dave
I've eliminated the message box and now a watch cursor appears.
Dave
|
| 213.7 | Screen handling just one problem? | THEFT::DAVE | Dave Lunn. | Wed Mar 16 1994 15:18 | 19 |
|
That's good... I don't need to report that it was definitely two popups where
you try to connect to a 'Console inactive' system then. 8?)
On the screen handling - further experiments show that all the problems I've
seen occur only when the initial system chosen is 'Console inactive' for
some reason. For example $CONSOLE CONNECT JURY leaves me at the Command:
prompt. Typing CONNECT <anothernode> correctly tries to report that I'm not
allowed to do that - but the screen doesn't get updated correctly. I guess
that it all stems from that initial connect failing and the screen problem
that happens at that time.
Can I just raise the last part of point 3 again. Typing CONNECT at the
Command: prompt after the 'Console inactive' message causes the window to exit.
This happens both from the C3 and from the dollar prompt.
Cheers,
Dave.
|
| 213.8 | | OPG::PHILIP | And through the square window... | Wed Mar 16 1994 15:53 | 11 |
|
>>Can I just raise the last part of point 3 again. Typing CONNECT at the
>>Command: prompt after the 'Console inactive' message causes the window to exit.
>>This happens both from the C3 and from the dollar prompt.
I have seen this and it has been fixed, as for the other stuff, we'll
take a look at it.
Cheers,
Phil
|