Hello Scott,
Please find my  inline comments regarding the NID bug mentioned by Igor for
point#3.

Regrads,
Varsha

----- Original Message -----
From: "Igor Kotelevsky" <[EMAIL PROTECTED]>
To: "Scott C. Best" <[EMAIL PROTECTED]>
Cc: "mailbox" <[EMAIL PROTECTED]>; "Kaboodle-devel"
<[EMAIL PROTECTED]>
Sent: Friday, July 05, 2002 6:54 PM
Subject: Re: Bog Report, 4 July


> Hello Scott.
> Please see my inline comments.
> - Igor
>
> > 2. Regarding the 100 ports that VNC auto-detection checks,
> >    lets do it this way. When I start up Kaboodle and open the
> >    PropPanel for a device and click on the VNC tab, Kaboodle
> >    should check just 10 ports: 5900-5909. *Only* if I click
> >    on "Check Again" should it scan the whole 100 port range.
> >    Also, I noticed that "Stop Check" isn't accessible, as the
> >    cursor is always an hourglass during a scan.
>
> Now scan work as you say:
> - just 10 ports: 5900-5909 when user click on the VNC tab;
> - whole 100 ports: 5900-5999 when user click "Check Again".
> The button "Stop Check" is accessible during a scan,
> despite the fact that the cursor is always an hourglass during a scan.
>
> > 3. If I startup a VNC server on a PC not running Kaboodle, I
> >    can go the the PropPanel for that device and connect. No
> >    problem. But the VNC Service icon is not listing the device
> >    as a server, and the VNC halo is not being put on the device
> >    correctly.
>
> I saw similar bugs.
> It was several days earlier.
> Please see my message
> http://www.geocrawler.com/lists/3/SourceForge/16728/0/9087814/.
> Then these bugs disappear.
> Please see my message
> http://www.geocrawler.com/lists/3/SourceForge/16728/0/9088195/.
> I discussed these bugs with Oleg and he said that he saw these bugs too.
> All these bugs look like some NID updating bug.
> The Problem consists in next - these bugs difficult to repeat.
> Now I don't see these bugs on my LAN.
>
Igor I have looked at the fuction "bool CEnumAllDevice::Enum()". The data
structure that the author is using may get deleted in the execution path and
get filled again for the GUI. The VNCautodetection thread is not synchonized
with the NID data updation. I think we need to synchonize the NID update and
VNCautodetection in searchnetwork manager thread.  Please suggest the other
options if you have.

> > 5. The VNC prop tabs still have the big "Debug buttons". Is
> >    there a way to make them appear *only* if we build the
> >    debug version, not the release version?
>
> The VNC prop tab doesn't have
> the big button "Test start up VNC Server(Debug only)"
> in release version, that button appear in debug version only.
> The VNC setup prop tab (viewer side) doesn't have
> button "Additional (debug mode).."
> in release version, that button appear in debug version only.
>
> I found that log files
> SessionVncServerLog.log, SessionVncViewerLog.log, ViewerThread.log
> appeared in release version.
> All these files is my VNC log files.
> Now above log files appear in debug version only.
>
>
>
>




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Got root? We do.
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel

Reply via email to