ausdilecce wrote:Hmm, this is a problem... gotta think about that one... focus is very hard to pre-plan, especially if the OS does stuff TB has no control over
.....
The dialup dialog is part of windows and the hang up prompt is part of TB. If you give focus to the hang up prompt, you are giving focus to the whole TB app, which will "hide" the dialup prompt.. this goes hand in hand with your previous point..
hmm.... we need AutoHangUp to ask the question BEFORE the OS connection is requested.
There must be some call (or trigger or event whatever it's called) from TB to the OS connection routine that says "get me connected". Then the OS goes through the dial up routine.
Is it possible for AutoHangUp to intercept that call from TB to the OS? Then AutoHangUp says to TB "what a second I've got to ask a question", then once the user has answered, AutoHangUp says to TB "OK, go ahead with what you were doing, ie request a connection from the OS".
I guess there are several ways of doing this:
1) Replace the TB coding that says "Call the OS to make the connection" with "call AutoHangUp and once AutoHangUp is ready then call the OS to make the connection"
2) Make AutoHangUp a middle man so TB calls AutoHangUp to make the connection, AutoHangUp asks the question and then passes on the request for a connection to the OS
3) A watch on a property that changes when the users clicks "Get Mail", AutoHangUp jumps in, pauses TB, asks the question, then lets TB carry on.
4) Is it possible to change the the action of the "Get Mail" command or button so it calls AutoHangUp instead? Then AutoHangUp passes on the "Get Mail" command to TB? I think we should have a chat with that chap who did that helpful "GetAllMail" button
5) others that I can't even imagine.....
richard_leeds wrote:- Eeither clicking on the online icon (bottom left) or menu option to go offline both force hang up. This covers situations where the user has stayed online.
ausdilecce wrote:Are you saying that's how it should be ?
I'm suggesting there could also be a manual trigger for the hang up as well as the automatic one. This would watch the online status, when the user changed to offline, it would trigger the hangup command. I appreciate not everyone would want that by default, but it's the behaviour most dial up users would expect when selecting "offline". There would be an option in the extensions to:
[ ] Hang up automatically when going offline (Default option)
[ ] Ask the user if they want to hang up each time they go offline
[ ] Turn off the feature
To be honest, I'm impressed you jumped stright to the automatic version! A simple "when TB goes offline, make the connection offline as well" would have made me quite happy.