The Perl code below will cause an access violation. Uncommenting the -name
parameter will fix it. Took a while to figure this out. The offending line
is in GUI.XS, Create(), line 4512:
strcpy( (perlud->szWindowName), perlcs.szWindowName);
Is this the proper mailing list to report bugs on?
I don't know much about the guts of Win32::GUI (or Win32 in general, or
POE for that matter), but would a combination of POE and Win32::GUI be
successful, or is Win32::GUI not stable enough yet? Or simply not
constructed for that sort of thing? To me the possibilities seem great,
but maybe I'm just
Erick J. Bourgeois wrote:
>> sorry, but where did you got this syntax?
>
> From the documentation in FileOp module.
oh, well, FileOp != Win32::GUI :-)
cheers,
Aldo
__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;
> sorry, but where did you got this syntax?
>From the documentation in FileOp module.
erick
never stop questioning
www.jeb.ca
- Original Message -
From: Aldo Calpini <[EMAIL PROTECTED]>
To: Erick J. Bourgeois
Sent: Monday, February 12, 2001 10:47 AM
Subject: Re: [perl-win32-gui-users] Sa
Erick J. Bourgeois wrote:
> Has anyone had success using the SaveAsDialog?
>
> I'm using the SaveAsDialog in the following way:
>
> my %param = (title => "SaveAs",
> filters=>{'Filter 1' => '*.txt;*.doc', 'Filter 2'
> =>'*.pl;*.pm'});
> my $file = SaveAsDialog %param, "foo
Erick J. Bourgeois wrote:
> I wish to prevent the user from choosing more than one item
> in a Listview and since I didn't find an option
> for -multisel, like in a ListBox, I have attempted to
> achieve this through the ItemClick event for a ListView.
>
> sub ListView_ItemClick {
> if ($Win->L
6 matches
Mail list logo
