RE: [perl-win32-gui-users] possible problem with GetOpenFilename

2001-01-10 Thread Jake Skinner
No wonder you were so keen on fixing the memory leak bug!!! :) Jake > stuff), and save a _whole_ byte of memory (for about 15 seconds).

Re: [perl-win32-gui-users] possible problem with GetOpenFilename

2001-01-10 Thread Sam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 same goes for GetSaveFileName. NB: also if you're a pedant (like me) then you can change filterlen += 2, to filterlen++ (so long as you change the pointer stuff), and save a _whole_ byte of memory (for about 15 seconds). > Sorry about essentially sp

Re: [perl-win32-gui-users] possible problem with GetOpenFilename

2001-01-10 Thread Sam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I had this problem before - I found a possible solution in the old archives > (at http-tech), but it involved recompiling (if I recall correctly, the > variable filterlen was not given a default value of 0, so when you specify a > filter, the pro

Re: [perl-win32-gui-users] possible problem with GetOpenFilename

2001-01-10 Thread Sam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry about essentially spamming this newsgroup, but I have a fix for the following problem (if anyone else is ever actually effected by it). in the GetOpenFileName XSUB; change to following code: int i, filterlen;

Re: [perl-win32-gui-users] possible problem with GetOpenFilename

2001-01-10 Thread Sean Healy
I had this problem before - I found a possible solution in the old archives (at http-tech), but it involved recompiling (if I recall correctly, the variable filterlen was not given a default value of 0, so when you specify a filter, the program tries to increment something that hasn't been set

RE: [perl-win32-gui-users] The memory leak problem (fixed, I hope ;)

2001-01-10 Thread Jake Skinner
Well done Sam! Well done Aldo!!!

[perl-win32-gui-users] possible problem with GetOpenFilename

2001-01-10 Thread Sam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 can anyone out there recreate this: from perl call my $filename = Win32::GUI::GetOpenFileName( -filter => [ "File type 1" => "*.ft1", "File type 2" => "*.ft2", ], ); now call this twice. The first time

Re: [perl-win32-gui-users] The memory leak problem (fixed, I hope ;)

2001-01-10 Thread Sam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Sam wrote: > > I said I'd report when I know more, so here goes... > > > > The problem isn't with DefWindowProc at all (in fact > > DefWindowProc doesn't do anything except default handling - > > duh!). My apologies for being misleading. > > no pr

RE: [perl-win32-gui-users] The memory leak problem (fixed, I hope ;)

2001-01-10 Thread BUESCHER,CONOR (HP-Corvallis,ex1)
Congrats to everyone on this great news! Conor Buescher HP Corvallis -Original Message- From: Aldo Calpini [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2001 4:52 AM To: Sam Cc: perl-win32-gui-users@lists.sourceforge.net Subject: Re: [perl-win32-gui-users] The memory leak problem

Re: [perl-win32-gui-users] a simple question

2001-01-10 Thread Jonathan Southwick
What you need is: $ModuleWindow->Caption("new title"); Jonathan Southwick Technical & Network Services Allegheny College, Meadsville, PA [EMAIL PROTECTED] - Original Message - From: "christopher sagayam" <[EMAIL PROTECTED]> To: Sent: Tuesday, January 09, 2001 9:50 AM Subject: [perl-wi

Re: [perl-win32-gui-users] The memory leak problem (fixed, I hope ;)

2001-01-10 Thread Aldo Calpini
Sam wrote: > 2/ give the Dialog XSUB an explicit block around the perl > interpreter calls it makes. I believe that this will work fine, > but I haven't tested it. you got it Sam! I added ENTER/SAVETMPS + FREETMPS/LEAVE inside the Dialog() loop (while (stayhere)) and it works like a charm now

Re: [perl-win32-gui-users] The memory leak problem (fixed, I hope ;)

2001-01-10 Thread Aldo Calpini
Sam wrote: > I said I'd report when I know more, so here goes... > > The problem isn't with DefWindowProc at all (in fact > DefWindowProc doesn't do anything except default handling - > duh!). My apologies for being misleading. no problem. even checking the obvious is helpful in such cases :-)