Hello Scott. About your #2. Yesterday I wrote about some not understanding of old Kaboodle code, which pertains to part of initialization VPN. The old code worked like next: 1. Any Kaboodle (PC1) always connected to the Gnutella server at start up: please see the line *InitializeVpn()* in the function *CEFController::Start(). 2. If PC1 received the message, which indicated that another Kaboodle (PCn) begins run in the same LAN, then PC1 disconnected from the Gnutella server: please see the line *InitializeVpn()* in the function *CEFController::OnRemoteNIDIn(). 3. If PC1 received the message, which indicated that another Kaboodle (PCm) finish run in the same LAN, then PC1 connected to the Gnutella server: please see the line *InitializeVpn()* in the function *CEFController::OnRemoteNIDIn().
Now Kaboodle must connect to the Gnutella server if it's Master only. Therefore I commented lines *InitializeVpn()* in the #2 and #3. I tested this within available beside me time only. About your #3. You wrote: > > If PC2 is already the Master, then this checkbox > > should be replaced with "This PC is currently the Kaboodle > > Master Node". Status: implemented. About your #4. Status: Using dropdown and combobox a user can set a PCn as the Master, but they cannot set a PCn as Non Master. About your #5 (positions of PC's in the GUI and in the dropdown) Status: I did not have time to to execute that thing. About your #6. Status: I did not have time to to execute the first part of that thing. There is standard GUI still. The second part of that thing was implemented earlier. If you need me to work anymore, then please contact Alexander. - Igor ----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, October 24, 2002 8:10 PM Subject: Re: Master Node bugs - bugs #1, #2 (fwd) > VK: > Hello! Could you please help answer Igor's question > about InitializeVpn() below? It's holding up the fixing of > some bugs with the Master Node code. > Thanks! > > -Scott > > ---------- Forwarded message ---------- > Date: Thu, 24 Oct 2002 18:41:29 +0400 > From: Igor Kotelevsky <[EMAIL PROTECTED]> > To: Scott C. Best <[EMAIL PROTECTED]> > Cc: Kaboodle-devel <[EMAIL PROTECTED]> > Subject: Re: Master Node bugs - bugs #1, #2 > > Hello Scott. > The bug #1 is fixed. > > About bug #2. > I saw that bug. > I found and fixed a some reason - > Kaboodle not correctly determined if it must set itself as the Master at > startup. > But I didn't completed that bug: > 1. The old code contained several (about 5) points of calling > InitializeVpn(). > 2. If a user sets a PC as Master, then Kaboodle must call InitializeVpn() > also. > My modification #2 had some conflict with #1: > Now if Kaboodle start as Non Master, then it do not call InitializeVpn(). > But if it receive Remote NID, then it call InitializeVpn() - it's old part > of source code. > I do not understand the reason of that code. > Above conflict has avoided - > I removed one calling of InitializeVpn() from the function > *CEFController::OnRemoteNIDIn()*. > I need some time for understanding in this more attentively and > some time for testing. > > Others bugs will be fixed later. > - Igor > > ----- Original Message ----- > From: "Scott C. Best" <[EMAIL PROTECTED]> > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > Sent: Wednesday, October 23, 2002 8:37 PM > Subject: Master Node bugs > > > > Igor: > > Heya. I'm trying to put all the bugs with the Master > > Node stuff into one email. > > > > 1. For some reason, a network printer's PropPanel has the > > Master Node selection stuff that should go only into the > > Network Icon PropPanel. > > > > 2. I've two Kaboodle's on my LAN, PC1 (WinNT) and PC2 (Win98). > > PC1 turned on first, so it should be the Master Node. When > > I start Kaboodle on PC2, I look in the Network Icon on PC1 > > and it says that PC2 is now the Master. When I look on PC2, > > though, it says that PC1 is the Master. When I look at the > > network traffic, both PC's are pinging the Active List of > > devices every 5 seconds (which only the Master Node should > > do). When I open the Network Icon, the value shown in the > > dropdown must be set to the current Master Node. This value > > must be NID sync'd across the whole network. > > > > 3. On PC1, the dropdown in the Network Icon says that PC2 is > > the Master Node. When I open the PropPanel on PC2, the > > selection box "Make this PC the Master Node" is ready to > > be checked. If PC2 is already the Master, then this checkbox > > should be replaced with "This PC is currently the Kaboodle > > Master Node". > > > > 4. Using these checkboxes and the dropdown in the Network icon, > > I am unable to change the Master from PC1. If I change it > > using the dropdown to PC2, click okay, then reopen the Network > > Icon, it still says PC1. If I select one of the checkboxes > > and click Okay, the dropdown in the Network Icon does not > > change. None of my changes affect the Master Node status. > > > > 5. If I move the PC2 icon in the GUI of PC1 to a new position, and > > then try to change the Master Node status using Kaboodle on > > PC2, the position of PC2 in the GUI reverts to where it was. > > Master Node status should not affect the position of devices > > in the GUI. > > > > 6. To change the Master Node, the user should have to do one > > of two things: > > > > * Open the PropPanel for the PC Device, select the > > Master Node checkbox, and click Okay. If they open > > another tab before clicking Okay, the checkbox > > should reset itself. If the click Cancel, no changes > > are made. > > > > * Open the Network Icon, select a new device in the > > dropdown, and click Okay. If they open another tab > > before clicking Okay, the dropdown should reset > > itself to the current Master. If they click Cancel, > > not changes are made. > > > > Those are the only two ways a Master Node can be changed. > > Please ignore any of my requests below which contradict this. > > Thanks! > > > > -Scott > > > > > > On Wed, 23 Oct 2002, Igor Kotelevsky wrote: > > > > > Hello Scott. > > > Please see my inline comments. > > > - Igor > > > > > > ----- Original Message ----- > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > Cc: <[EMAIL PROTECTED]> > > > Sent: Tuesday, October 22, 2002 9:56 AM > > > Subject: Re: Misc bugs, 18 Oct 02 > > > > Igor: > > > > Sorry, missed something: > > > > > > > > 7. When I select a new Master Node in the Network Icon dropdown > > > > and hit OKAY, it should be updated everywhere. It's not. If > > > > I change it, hit OK and immediately open the panel again, the > > > > same old data is there. Also, if I change the dropdown, click > > > > on the Remote Network tab, then back to the main tab, the > > > > dropdown should show the current Master, *not* my halfway > > > > made change. > > > > > > Sorry, I think there is some miscellaneous understanding. > > > Earlier you wrote: > > > > > > > 6. Please remove the text in the Network Icon which reads > > > > > > > "Status of the PC will be changed...". Also, please > > > > > > > remove the "+" and "-" signs from next to the Device > > > > > > > names in the dropdown. All I want in that dropdown list > > > > > > > are the Kaboodle PC's on my LAN, that's it. Whichever > > > > > > > one is selected when I hit "OK" becomes the Master. > > > These exact things were implemented. > > > > > > You wrote: > > > > > > > Whichever one is selected when I hit "OK" becomes the Master. > > > A. I implemented that like next: > > > - If a PC didn't was the "Master" and a user hit "OK", > > > then the PC becomes the Master. > > > - If a PC already was the "Master" and a user hit "OK", > > > then there is not any change. > > > > > > Also above action will take place *only* > > > if user change that dropdown like you asked: > > > ----- Original Message ----- > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > > Sent: Friday, October 18, 2002 10:39 PM > > > Subject: Re: [Kaboodle-devel] Misc bugs, 18 Oct 02 > > > > To clarify on #6: if the user selects a new Master > > > > machine in the Network Icon, and then clicks Remote Networks > > > > tab before hitting Okay...the Master Node status should *not* > > > > change. Only if they change it *and* hit Okay should it be > > > > updated. > > > B. I implemented that like next: > > > Kaboodle stores the selected dropdown when it opens that tab. > > > After a user hit Okay, then it compares selected dropdown and it > initialized > > > index. > > > If these values are identical, then Kaboodle don't make any change. > > > If the user clicks Remote Networks tab, then Kaboodle don't make any > change > > > also. > > > > > > C. About listing of the dropdown. > > > Kaboodle lists all PC's, which runs Kaboodle it the LAN. > > > If there is the Kaboodle, which is the Master, > > > then that device will be selected in the dropdown. > > > If there are several Masters, then the first (in lexicographically > ordered) > > > Master device will be selected in the dropdown. > > > If there is not any Master, then the first (in lexicographically > ordered) > > > Kaboodle device will be selected in the dropdown. > > > > > > I cannot understand what of my implementations #A-#C are invalid. > > > > > > > 8. In the main Prop Panel for a Kaboodle PC, there is a checkbox > > > > saying "Make this PC the Kaboodle Master Node" and it's always > > > > checked. Please change this so that it's always unchecked. If > > > > the user checks it, and hits Okay, it should update the Master > > > > Node status everywhere just like in #7. > > > That checkbox isn't always checked. > > > It is checked if a PC is the Master. > > > It is unchecked if the PC isn't the Master. > > > So a user can see if the PC is the Master or not. > > > I implemented what you asked: > > > - Above checkbox is unchecked always. > > > (So a user *cannot* see if the PC is the Master or not.) > > > - If a PC didn't was the "Master" and a user hit "OK", > > > then the PC becomes the Master. > > > - If a PC already was the "Master" and a user hit "OK", > > > then there is not any change. > > > So the user can set a PC as the Master, but cannot set it as Non-Master. > > > > > > > > > > On Tue, 22 Oct 2002, Scott C. Best wrote: > > > > > > > 6. Please remove the text in the Network Icon which reads > > > > > > > "Status of the PC will be changed...". Also, please > > > > > > > remove the "+" and "-" signs from next to the Device > > > > > > > names in the dropdown. All I want in that dropdown list > > > > > > > are the Kaboodle PC's on my LAN, that's it. Whichever > > > > > > > one is selected when I hit "OK" becomes the Master. > > > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > To clarify on #6: if the user selects a new Master > > > > > > > machine in the Network Icon, and then clicks Remote Networks > > > > > > > tab before hitting Okay...the Master Node status should *not* > > > > > > > change. Only if they change it *and* hit Okay should it be > > > > > > > updated. > > > > > > > > > > > > The text in the Network Icon which reads > > > > > > "Status of the PC will be changed..." removed. > > > > > > Signs "+" and "-" removed also. > > > > > > Only if a user change selected dropdown *and* hit Okay should it > be > > > > > > updated. The user can set a PC as the Master Node from that tab. > > > > > > The user *cannot* set a PC as the "Non Master Node" from that tab. > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net emial is sponsored by: Influence the future > > > of Java(TM) technology. Join the Java Community > > > Process(SM) (JCP(SM)) program now. > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en > > > _______________________________________________ > > > Kaboodle-devel mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel > > > > > > > > > > ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
