VK:
Hello! Two quick bugs to report:
1. The app crashes with an access violation at startup in a
specific manner. Right after you startup the app, with a
fresh registry, open the VNC PropPanel, click on the
Viewer Property Tab, and quickly "Cancel". The app crashes
with an access violation" "this instruction at 0xc00000005
referenced memory at 0xc0000005". the debugger takes me to
VncRunningAutoDetect.cpp's CGlobalRunningAutoDetect::ClearAll
right at the "delete" line. The "this" pointer looks fine
to me, as do the other variables and pointers. Hope you
can re-create it on your end.
2. The bug#6 (the default 5 groups coming back) still happens
when a new network device is discovered. The other bugs I
mentioned look squashed (thanks!).
Some comments to your comments:
> I have added the placeholders for the Services (VPN and VNC). Please
> see if those are useful to you.
They are, thank you. I'll speak with Igor@Akmosoft about
completing that interface.
> The bug #6 is fixed only for the change in the device properties. If
> you click on tray icon then the application will again start with 5
> groups. I cannot fix this entirely until NID module team finishes their
> work because the NID data contains only PCs and printers and not the
> association with the groups and group hierarchy.
>
> I had tried to make the data persistence with the registry but that
> may disturb the current system as I added the group icons and service
> icons at the network hierarchy under the NIDManager. This addition is
> just to display the property pages for testing purpose.
Since this version of Kaboodle doesn't need to be backwards
compatible with previous versions, I think this hierarchy change is
good enough for release, not just testing purposes. Positioning
groups in the hierarchy below network and before device seems best
to me.
As for the service icons, they should be at the same level
as Devices in the hierarchy. Devices are auto-detected by ping'ing
their IP address; services will be (someday) auto-detected by
looking for their API's.
> I think working on GUI data persistence on NID hierarchy freeze will
> make it more robust and well designed. Even if I add data in the
> registry I need the exact position of group and services NID data
> structure as many modules get the data from NID data hierarchy with some
> assumptions. The assumptions at present are: 1. First network will be
> local 2. The network will have all the PCS. 3. All the printers will be
> under the masterPC etc. I cannot just add the groups and services at any
> place.
>
> Please suggest the remedy to the problem.
The short-term fix is to re-write the NID as you need it
and update the modules which "make assumptions" so that they work
with your changes. The longer-term fix is to reinvent a lot of
the NID code.
Sorry; beyond that, I have no suggestions. What do you
suggest?
> I have tested remote networks with dummy data. Can you please test the
> GUI with VPN?
There's still a bug in the code which is preventing me
from creating a VPN. But doing this test is on my very-short list
of things to do.
-Scott
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
