Hello Igor,
I have added the code for the synchronization of NID and VNC autodetection
start. I have synchronized the CNetworkLocalView data update and the VNC
auto detection as Your code is using the data from the local variable of the
CNetworkLocalView  m_LocalIcons . I think this synchronization will be
robust if you use the data from NID module directly from the
NIDManager/NIDnetwork. But the VNC autodetection crashes after finding the
VNC for first device. Can you please take a look it.

Regrads,
Varsha

----- Original Message -----
From: "Scott C. Best" <[EMAIL PROTECTED]>
To: "Igor Kotelevsky" <[EMAIL PROTECTED]>
Cc: "mailbox" <[EMAIL PROTECTED]>; "Kaboodle-devel"
<[EMAIL PROTECTED]>
Sent: Wednesday, July 10, 2002 10:20 AM
Subject: Re: [Kaboodle-devel] Some changes in LAN detection needs


> Igor, VK:
>
> Please keep me posted of what you two decide is the best
> solution for getting VNC autodetection, NID updating, and NID
> synchronization all working together.
>
> -Scott
>
> On Tue, 9 Jul 2002, Igor Kotelevsky wrote:
>
> > Hello Varsha.
> > We can use different synchronization technique, but it doesn't matter in
> > current case.
> > You say that
> > > The VNC autodetection is in the right place.
> > But it may be that in this place LAN detection doesn't finish.
> > This means that it is not right place.
> > Also may be Kaboodle needs to make additional check it this right
place -
> > is there any device except my PC .
> > I can insert that check in my "VNC autodetection" code.
> > But it seems to me that it is not correct.
> > As I wrote early, VNC autodetection must be initialized only after
> > > a) - determination of local network is completed;
> > NID updating cannot change LAN configuration
> > (it seems to me that if it is so, then it is bug, which must be fixed.)
> > - Igor
> >
> > ----- Original Message -----
> > From: "mailbox" <[EMAIL PROTECTED]>
> > To: "Igor Kotelevsky" <[EMAIL PROTECTED]>; "Scott C. Best"
> > <[EMAIL PROTECTED]>
> > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]>
> > Sent: Tuesday, July 09, 2002 4:28 PM
> > Subject: Re: [Kaboodle-devel] Some changes in LAN detection needs
> >
> >
> > > Hello Igor,
> > > We are posting the messages to the respective threads. One for NID
update
> > > and other for VNC autodetection but NID updating may not get executed
> > fully
> > > when your VNC thread gets the CPU time.  This is the reason that is
why
> > you
> > > are getting only one device in the list. As I mentioned before that we
> > need
> > > the synchronization technique. May be an events would be the best
solution
> > > for this. Some event will be set on the NID update and your code can
wait
> > > till that event gets signaled.  The VNC autodetection is in the right
> > place.
> > >
> > > Regards,
> > > Varsha
> > > ----- Original Message -----
> > > From: "Igor Kotelevsky" <[EMAIL PROTECTED]>
> > > To: "mailbox" <[EMAIL PROTECTED]>; "Scott C. Best" <[EMAIL PROTECTED]>
> > > Cc: "mailbox" <[EMAIL PROTECTED]>; "Kaboodle-devel"
> > > <[EMAIL PROTECTED]>
> > > Sent: Monday, July 08, 2002 3:01 PM
> > > Subject: [Kaboodle-devel] Some changes in LAN detection needs
> > >
> > >
> > > > Hello Varsha.
> > > > I found some changes in LAN detection - it works more quickly now.
> > > >
> > > > But I found following bug.
> > > > I cleared Kaboodle registry settings on my PC.
> > > > There is not other running Kaboodle on my LAN.
> > > > I started Kaboodle on my PC.
> > > > VNC autodetection doesn't begin.
> > > > (That bug doesn't appear if other PC runs Kaboodle at this time.)
> > > >
> > > > The reason is next.
> > > > Kaboodle has only single "NID PC device" (my PC) when
> > > > CSearchNetworkManager thread
> > > > posts the message CMainFrame::m_nMsgBeginVncAutoDetection
> > > > to the object CMainFrame at first moment.
> > > >
> > > > As I wrote to you at 04.07.2002
> > > > (http://www.geocrawler.com/lists/3/SourceForge/16728/0/9097093/)
> > > > > Kaboodle can begin VNC Autodetection
> > > > > when are executed following conditions:
> > > > > a) - determination of local network is completed;
> > > > > b) - each PC in network has valid IP address and valid MAC address
> > > > > (MAC address uses for storing result of VNC Autodetection).
> > > > In the current version the condition #a is not executed.
> > > > Please replace calling of VNC autodetection in a *valid* placement.
> > > > In that valid placement both conditions #a and #b must be executed.
> > > > - Igor
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This sf.net email is sponsored by:ThinkGeek
> > > > Oh, it's good to be a geek.
> > > > http://thinkgeek.com/sf
> > > > _______________________________________________
> > > > Kaboodle-devel mailing list
> > > > [EMAIL PROTECTED]
> > > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> > > >
> > >
> > >
> >
> >
>
>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Two, two, TWO treats in one.
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel

Reply via email to