Igor:
> Therefore I have change above function:
> BOOL CNIDDevice::Connect(BOOL bFlag)
> {
> if (bFlag) m_Attributes.m_nFlags |= DEVICE_CONNECTED;
> else m_Attributes.m_nFlags &= ~DEVICE_CONNECTED;
> return true;
> }
>
> Now the NID update bug doesn't appear.
> All above changes are in the CVS Server.
I agree that this works much better now. I tested it
this morning and it looks good.
I still see one more place where the NID is not
synchronized, though. If I start Kaboodle on PC1, it discovers
a VNC server on one of my non-Kaboodle machines. It puts a
halo on this device correctly. Then I start Kaboodle on PC2.
It does the following strange things:
1. It does its own network scanning and OS detection, rather
than just getting this information from the NID.
2. There is no halo on the non-Kaboodle machine. The non-
Kaboodle machine is also not listed in the VNC Viewer list
in the Service icon. However, if I open the Prop Panel for
the non-Kaboodle device and go to VNC Setup, it reads at
the top "when connecting to NonKaboodlePC from PC1 use
these settings". Connect is greyed out though. To fix this,
I need to hit Check Again. Then all of the problems go away.
It seems to me that most of the data the GUI uses is
stored in the NID that is sync'd with other Kaboodle users,
but some other information is not stored in the NID. I think
the only information that should *not* go into the NID, and
should instead be stored locally, are passwords. Can you think
of any other data which should not be synchronized?
-Scott
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
