Oleg:
Heya...
> 1. Icons.
> >>>The VNC halo appears at odd times. It's there with
> >>>the old EchoFree halo when I first startup. Then,
> >>>as soon as I click a dependant device
> >If you have a serial printer driver installed on
> >the machine you're running Kaboodle on, it should create
> >an icon for it.
>
> Thank you. It really helped.
> Fixed, the source is attached.
The icon halo's don't change at weird times now. Then
again, the check-mark that used to come up when you clicked on
a "dependant device" doesn't come up either. I'll check to see
if that's because of the VNC halo "getting in the way".
> 2. Null pointers.
> >The "this" pointer is having problems still.
> >I've setup the second WinNT machine so that it crashes. The
> >"debug" result of the crash is open in WinNT on the machine
> >you VNC into.
>
> We had a look at it. File EFController.cpp had the following code:
>
> [snip]
>
> We inserted several ifs, just like we did it before
> Unfortunately, we do not know how many such hidden bugs
> there are. I am afraid, the work of finding and fixing them
> is out of our work plan.
I'm concerned about what changed between versions 0.72
and 0.75 that resulted in this null pointer being run into all
the time. In the version you sent last night, it's gotten to the
point that two PC's running Kaboodle on the same LAN don't even
find each other: they display different network topologies until
one or both of them crash. Not pretty. I think you'd agree with
me that this wasn't happening before the VNC work began.
I'm going to go backwards in time and find the latest
version that does run this in a stable manner. Then I'll diff
the .cpp's in the NID directory and find out which ones changed.
cheers,
Scott
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
