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

[<Eoi...@de...>]

I'm getting this=20
using Windows 2K

Unquoted string "re" may clash with future reserved word at =
File/Basename.pm
lin
e 131.
couldn't find diagnostic data in C:\Perl\lib/pods/perldiag.pod =
C:\Perl\bin .
C:\
DOCUME~1\EOIN_B~1.EUR\LOCALS~1\Temp\Oasis\{BBD1CC5C-1D7C-4ED5-AB92-FD148=
6CB9
74E}
\ . C:\Perl\bin\Oasis.exe at Diagnostics.pm line 241.
BEGIN failed--compilation aborted at Oasis.exe line 21.

Rgds  Eoin :

mailto:Eoi...@de...



-----Original Message-----
From: Johan Lindstrom [mailto:jp...@bo...]
Sent: 18 April 2001 16:20
To: per...@li...
Subject: RE: [perl-win32-gui-users] Perl Oasis


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=20
perl56.dll file included. I guess that is the problem.

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.

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=20
present there is the "latest release".


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.

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.

After having fiddled with this for a couple of hours yesterday, it =
seems=20
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=20
disapperars.

Most of the time 2) isn't relevant, so the program works. I still =
haven't=20
pinpointed this one.

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.

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... :/


/J

--
Johan Lindstr=F6m, Sourcerer, Boss Casinos Ltd, Antigua
jp...@bo...


_______________________________________________
Perl-Win32-GUI-Users mailing list
Per...@li...
http://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users