Heyaz. I got to evaluate the Bug#3 fix today with the
latest code. I had to manually copy over the needed IPHlpApi
related files, and adjust path names accordingly to get it to
compile, but it worked. Going forward, we should include the
required .h files in our own Include directory, and point to
them correctly.

        Anyhow. Three small fixes needed to your Bug#3 fix:

1. Please change "Autostart Now" to just "Start Now" as you
   suggested.

2. When VNC is running in App-mode, I can see the icon in my
   service tray. When I use Kaboodle to "Start Now", it adds
   another icon there, but the original doesn't go away. I've
   added 3 or four, and there ends up being a little parade of
   icons. When I mouseover those icons, the inactive ones go
   away, but I think this should refresh automatically.

3. When VNC is running in App-mode, I can open the Properties
   for it and de-select "Accept Socket Connections". Then close
   it. Via Kaboodle, when I Auto-start VNC, it "inherits" the
   de-selection of "Accept Socket Connections", and so Kaboodle
   reports the "Sorry...was unable to start WinVNC..." message.
   The app is actually running, it's in the task bar, it's just
   not accepting socket connections. The fix: when Kaboodle is
   auto-starting, it should activate "Accept Socket Connections"
   every time.

        Thanks!

-Scott


On Thu, 20 Mar 2003, Kaboodle wrote:

> Bug #3 is fixed according with your last guidelines.
>
> Before trying to kill current VNC server Kaboodle check the new settings:
>
> - does new entered server file exists
> - is new entered port number free
>
> If these checks fail then Kaboodle generates an appropriate notification message
> ( examples are attached as JPG files ) and does not trys to stop current server
> and start new one.
> If these checks are OK then Kaboodle stops current server (if it is running)
> and try to start new server with new settings.
>
> I don't know how to simulate a fault when server exe name is OK but
> port number is free but is not fit.
> But I can simulate a fault when server exe name is bad.
> The screenshot of notification message in this case is attached as JPG file.
>
> I'll ckeck in the updated sources in your repository now.
>
> Is it enough or you consider necessary to add/change something else?
>
>



-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel

Reply via email to