T.R | Title | User | Personal Name | Date | Lines |
---|
2217.1 | Full design spec please :-) | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Fri Feb 05 1993 11:22 | 4 |
| Um, how would this work if you were in an editor? Especially if it
wasn't one of ours?
Graham
|
2217.2 | Ugh! | HORLIX::paul | I'm pink therefore I'm SPAM | Fri Feb 05 1993 13:36 | 5 |
| Well, I don't like this idea at all - it's too intrusive for me (I'm
assuming you'd have to do something to get rid of the message box.)
FWIW,
Paul.
|
2217.3 | It's ment to be intrusive BUT can be turned off | BUSHIE::SETHI | Man from Downunder | Mon Feb 08 1993 04:52 | 27 |
| Hi Graham and Paul,
RE: .2
>Well, I don't like this idea at all - it's too intrusive for me(I'm
>assuming you'd have to do something to get rid of the message box.)
Don't forget that the /broadcast_handler=noforce will disable the
message box from being displayed, so if users are worried about it
being too intrusive it can be turned off. To get rid of the box just
enter screen exit.
re: 1
We can display the Interupt Menu from within an editor both WPS-PLUS and
WordPerfect, so I don't see why the Message Box could not be displayed.
If this is not possible perhaps the message text should only be
displayed on line 24, while the user is in the editor.
The reason why I put forward this suggestion is that when I was working
at a large site we were hoping that this facility would become avaiable.
In an emergency we had to shutdown the system it would be a good facility
to force users to read the message.
Well that's all for now,
Sunil
|
2217.4 | More details of your design please :-) | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Mon Feb 08 1993 21:10 | 13 |
| We can display the interrupt menu from within those editors, because
the writers of those editors chose to write code to do so. If we
invented some new functionality for broadcasts, all the editor writers
would have to fix it too.
What we (OA$MAIN) need is a way to catch the broadcast even when the
editor has control of terminal I/O, and display it somewhere, which
will look OK regardless of what is on the screen, won't mess up the
screen, can be overpainted by whatever is using the screen without it
having to do any new code, and can be ignored if people don't want to
acknowledge it....
Graham
|
2217.5 | Thinking thinking ... | BUSHIE::SETHI | Man from Downunder | Tue Feb 09 1993 05:06 | 18 |
| Hi Graham,
I will go into thinking mode, hopefully I will put my idea's forward in
a reply here. I knew that the editor will be the problem area and
guess what .... I wanted to put my head in the sand ;-).
The interesting part would be the displaying of the message when a user
is in the editor. Also rather than using EXIT SCREEN a CONTROL W or R to
refresh the screen would be a better idea.
This and next week I will have my skates on finnishing off my
presentation on DEC MAILworks. Than the dreaded day arrives on the
22nd, I'll either be a start or gobbled up :-). So if you don't hear
from me you know why.
Regards,
Sunil
|
2217.6 | How about a background task to handle the message ? | BUSHIE::SETHI | Man from Downunder | Mon Feb 22 1993 03:43 | 21 |
| Hi Graham,
I can only think of a background task that traps the broadcaste message
and displays a Window on the users terminal. The editors would not
have to be changed to handle this as the task would do an interupt of
the main process before displaying the window than exit leaving the
windown on the screen. The user would enter control W or R to refresh the
window.
>can be ignored if people don't want to acknowledge it....
The whole point of having this was to force people to take notice of
it. Like the system will be shutdown in 5 mins please logoff or the
building is burning please do a runner ;0) type of messages.
I don't know if the above would be possible but it would be a nice
feature to have. Maybe it's alot of work for a nice feature !!!!
Regards,
Sunil
|