Nhat-Hung LAM wrote:
The binary also did not work for me (Windows NT 4 - SP6).
The binary was created as a "freestanding" PerlApp, but without the
perl56.dll file included. I guess that is the problem.
The new binary is now totally freestanding, i.e. it includes the perl56.dll
file. I hope that solves the problem. If not, please let me know.
A new release with the new binary and a few fixed defects is available here:
http://www.bahnhof.se/~johanl/perl/Oasis/
I haven't begun to name or date-tag the releases yet, so whatever is
present there is the "latest release".
Regarding the problem with the application chrashing when you double click
on a module to load it; I have confirmed the defect. I can reproduce it. I
still haven't been able to create a simplest-possible-case to reproduce it.
I have the Visual C++ debugger installed, and the error message I get is
something like 'The instruction at "xxx" referenced memory at "xxx". The
memory could not be "read".', which presumably means that the app tried to
access memory outside the application's memory space.
After having fiddled with this for a couple of hours yesterday, it seems
related to three things:
1) The fact that I Clear() the tree view
2) Certain data in the tree view when Clear() is called
3) The fact that the DblClick() event is triggered
If I don't Clear() the tree view when I load a new module, the problem
disapperars.
Most of the time 2) isn't relevant, so the program works. I still haven't
pinpointed this one.
If I don't actually double click on the node, the problem disappears. If I
call the DblCLick() sub from e.g. a NodeClick() event or a button Click()
it works fine.
My initial guess is that it is related to mouse events fired at or handled
by already-deallocated nodes in the tree view. Or something... :/
/J
--
Johan Lindström, Sourcerer, Boss Casinos Ltd, Antigua
[EMAIL PROTECTED]
