RE: [perl-win32-gui-users] Perl Oasis

[Lam, Nhat-H. <Lam.Nhat-Hung@PMINTL.CH>]

Johan,

I got downloaded the new binary but it does not work as well. Nothing
happened when starting it, program just exited without any error =
message!

I installed WIN32-API 0.20 (thanks Aldo :-)) and I can start it from =
source
code now.
Do you plan to make it support for Notepad editor as well? As UltraEdit =
is a
shareware and not all people have it!

Thank you
Nhat-Hung LAM

> -----Original Message-----
> From:	Johan Lindstrom [SMTP:jp...@bo...]
> Sent:	Wednesday, April 18, 2001 5:20 PM
> To:	per...@li...
> Subject:	RE: [perl-win32-gui-users] Perl Oasis
>=20
> Nhat-Hung LAM wrote:
> >The binary also did not work for me (Windows NT 4 - SP6).
>=20
> The binary was created as a "freestanding" PerlApp, but without the=20
> perl56.dll file included. I guess that is the problem.
>=20
> The new binary is now totally freestanding, i.e. it includes the
> perl56.dll=20
> file. I hope that solves the problem. If not, please let me know.
>=20
> A new release with the new binary and a few fixed defects is =
available
> here:
> http://www.bahnhof.se/~johanl/perl/Oasis/
>=20
> I haven't begun to name or date-tag the releases yet, so whatever is=20
> present there is the "latest release".
>=20
>=20
> Regarding the problem with the application chrashing when you double =
click
>=20
> on a module to load it; I have confirmed the defect. I can reproduce =
it. I
>=20
> still haven't been able to create a simplest-possible-case to =
reproduce
> it.
>=20
> I have the Visual C++ debugger installed, and the error message I get =
is=20
> something like 'The instruction at "xxx" referenced memory at "xxx". =
The=20
> memory could not be "read".', which presumably means that the app =
tried to
>=20
> access memory outside the application's memory space.
>=20
> After having fiddled with this for a couple of hours yesterday, it =
seems=20
> related to three things:
>=20
> 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
>=20
> If I don't Clear() the tree view when I load a new module, the =
problem=20
> disapperars.
>=20
> Most of the time 2) isn't relevant, so the program works. I still =
haven't=20
> pinpointed this one.
>=20
> If I don't actually double click on the node, the problem disappears. =
If I
>=20
> call the DblCLick() sub from e.g. a NodeClick() event or a button =
Click()=20
> it works fine.
>=20
> My initial guess is that it is related to mouse events fired at or =
handled
>=20
> by already-deallocated nodes in the tree view. Or something... :/
>=20
>=20
> /J
>=20
> --
> Johan Lindstr=F6m, Sourcerer, Boss Casinos Ltd, Antigua
> jp...@bo...
>=20
>=20
> _______________________________________________
> Perl-Win32-GUI-Users mailing list
> Per...@li...
> http://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users