Igor:
> > ... When the user first activated ""Allow only users..." and hit "Okay",
> > we show a MessageBox saying "Please restart your VNC Service for
> > these changes to take effect". We should just rely on the user
> > doing this. Or, of course, we could have Kaboodle send a restart
> > signal to the VNC service...but I don't think we know how to do that.
>
> It seems to me that Kaboodle can do it.
> 1) Shut down VNC server.
> 2) Save data into the VNC server registry.
> 3) Restart VNC server.
How about this: have the MessageBox say: "The VNC Service needs
to be restarted for these changes to take effect". There can be two
buttons: "Let Kaboodle do this now", "I'll do it myself later". If
the user clicks the first button, we do what you suggest.
> I think that
> > ... When the user first activated ""Allow only users..." and hit "Okay"
> or when Kaboodle startup and check option "Allow only users..."
> then Kaboodle must check if independent VNC server is running.
> If independent VNC server is not running then Kaboodle execute #2.
> If independent VNC server is not running then Kaboodle prompt
> "Kaboodle needs to restart your VNC server for setting "Allow only
> users..." to take effect. Proceed?"YES/NO.
> If user replies YES, then Kaboodle execute #1, #2, #3.
>
> There is only one thing that I don't know how to do.
> I don't know how to define that independent VNC server is used by third
> part.
> We should just rely that if user replies YES, then user knows what he do.
That sounds right.
-Scott
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
