Hello, Scott. >Hello! Hope you're feeling better. Thank you. I am answering from home and tomorrow I will write to you from work.
>Only problem is that I get this message after I shutdown >the VNC server which should have shutdown by itself (it stayed up >when I gave it the wrong password). If the server is "auto-shutdown" >then I shouldn't get this message. But don't worry about this; >see below. You mean it works differently when the password is wrong... Kaboodle does the same regardless if the password is correct or incorrect. I think this message does not have to pop up at all. You have wrote me about something like that a couple of weeks ago. I arranged it so that client checks in cycle if the VNC Viewer is running. If it does not, then a special user-defined message is sent to the partner and the above message pops up. I will see to make sure the server shuts down silently. >Okay, now for the longer idea. I think the idea of Kaboodle >... Yes, the idea is not bad. But I am afraid it will not protect us against the situation when a requested connection is not established. When you click "Connect", Kaboodle begins authorizing and no response is received. That happens often and we must see if it is specific to my configuration only or common. As for the algorithm you suggested I think there will be no problem implementing it. -Igor _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
