RE: [wxperl-users] wxPerl "weirdness"

[Casey W. <wil...@nc...>]

Ok, I'll work on putting something together.  This is a straight script
without Perlapp.  I fixed some of the problems by putting everything in
the same file instead of using .pm's.  I dunno why that would make a
difference, but it did.  I'm probably subtly doing something wrong, that
won't be reproduced in a smaller script, but I'll give it a go. :)
Also, this is using the original events.pm, not my version with
everything in the @EXPORTS_OK array.

Thanks for your time!

-Casey

-----Original Message-----
From: wxp...@li...
[mailto:wxp...@li...] On Behalf Of Mattia
Barbon
Sent: Friday, November 23, 2001 4:02 PM
To: wxp...@li...
Subject: Re: [wxperl-users] wxPerl "weirdness"


> Hey Guys,
> 	I'm wondering if anyone has gotten results anything like I'm
getting.  
> I can change very little things in a program, and it will cause wxPerl

> to crash.  Also, I added an event and now default text
Crash like a popup talkig about access violation/etc or something else?

> shows up as *'s.  I know I'm being very non-specific, I'm just
wondering
> if anyone else has had weird things happen like this.  I'd be happy to

> send off my code for perusal.
If you could make a small example that consistently reproduce the
problem it would be perfect. Are you using threads? Are you seeing this
just with perl2exe, or on 'normal' scripts too?

> I *am* running on XP Pro, would that be a problem?
It should not

Regards
Mattia

_______________________________________________
wxperl-users mailing list
wxp...@li...
https://lists.sourceforge.net/lists/listinfo/wxperl-users