perl-win32-gui-users — Using the Win32::GUI Perl extension

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

[Sam <sa...@se...>]

-----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 problem. even checking the obvious is helpful in such
> cases :-)
> 
> > The memory usage in the task manager thingee is useful, but 
> > inherently misleading. It isn't a cache allocation thing or
> > anything like that, again sorry for being misleading.
> >
> > The problem is with the C-perl interface. The WindowMsgLoop
> > needs a good perl start, and end block:
> > dSP;
> > ENTER;
> > SAVETMPS;
> >
> > ....
> >
> > FREETMPS;
> > LEAVE;
> 
> unfortunately not. WindowMsgLoop, itself, does not actually
> call the Perl interpreter: the various DoEvent_* functions
> performs the needed calls, and they all have (SAVE|FREE)TMPS
> blocks. I tried, just to give it a try, to make the changes
> you suggested to WindowMsgLoop, but nothing changes.
> 
> > This is because it calls into the perl interpreter. The Dialog
> > XSUB doesn't need those blocks explicitly however because they
> > are added by xsubpp. However because the Dialog XSUB pretty much
> > never exits (and therefore calls FREETMPS) it accumulates TMPs. 
> > There are (I believe) two ways to fix this:
> > 1/ make the dialog XSUB return after processing one message, 
> > and call it from perl like
> > while( Win32::GUI::Dialog() ) {
> > }
> 
> this is a good hint. unfortunately, it is not a solution.
> there is already a one-go Dialog XSUB, which is called
> DoEvents. I tried replacing the Dialog() call with this:
> 
> 1 while ( Win32::GUI::DoEvents != -1 );
> 
> and indeed, there is no apparent memory leak!
> 
> BUT, the processor is busy at 100% while the Perl
> program runs: this is because the while loop, even if
> 'void', does consume CPU time. too bad :-(
That's because it uses PeekMessage, which returns immediately 
regardless of whether or not there are any messages waiting.

> BUT, this is a first approach to a possible solution,
> because it seems to isolate the problem in the Dialog()
> XSUB. I'll try to debug it and see if I can understand
> something more.
> 
> > 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. I implemented (1) in my copy
> > of win32::GUI.
> 
> what do you mean by 'interpreter calls' here?
> 
> > NB:
> > It may be necessary to add blocks in other places (in fact
> > I'm sure of it), but this is the only problem I am aware of.
> > I can't create and distribute a patch on work time, but in my own
> > time (of which I have very little unfortunately) I will create
> > a patch for 0.0.502, and send this to Aldo, if he so desires.
> 
> please do so if you can :-)
> 
> 
> cheers,
> Aldo
> 
> __END__
> $_=q,just perl,,s, , another ,,s,$, hacker,,print;
> 
> 
> 
> _______________________________________________
> Perl-Win32-GUI-Users mailing list
> Per...@li...
> http://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
> 



-----BEGIN PGP SIGNATURE-----
Version: N/A

iQA/AwUBOlwquJsRND2Z+TaWEQJEPwCeLjIAiDb1DHzs8woIpcIpaV7u3JEAnR4G
38Dh5N9HX44Guqr612WBFf6Y
=mvOy
-----END PGP SIGNATURE-----

Sam Jacobson
R & D Manager / Software Engineer
Selective Communications
Ph +64 9 302 1142
www.selective.co.nz

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

[BUESCHER,CONOR (HP-Corvallis,ex1) <con...@hp...>]

Congrats to everyone on this great news!

Conor Buescher
HP Corvallis

-----Original Message-----
From: Aldo Calpini [mailto:da...@pe...]
Sent: Wednesday, January 10, 2001 4:52 AM
To: Sam
Cc: per...@li...
Subject: Re: [perl-win32-gui-users] The memory leak problem (fixed, I
hope ;)


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.
there is a small memory increase, but it's completely
acceptable (some k's when you do something in the window
at startup, click buttons, etc. but nothing when you simply
move the mouse around).

I think that the problem is in the magical stuff I've
added to support windows-as-hashes (eg. the TIEHASH stuff
that permits $Window->{-text}); since doing hv_fetch()
on a tied hash really calls the Perl sub FETCH on that
object, TMPs are really created (it seems).
hv_fetch alone would have not required a (SAVE|FREE)TMPS
block, but the magic behind it apparently does.

I will release a new version very soon with this nasty,
nasty, nasty bug finally *fixed* forever :-)

cheers,
Aldo

__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;



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

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

[Jonathan S. <jso...@al...>]

What you need is:

$ModuleWindow->Caption("new title");

Jonathan Southwick
Technical & Network Services
Allegheny College, Meadsville, PA
jso...@al...


----- Original Message ----- 
From: "christopher sagayam" <chr...@ya...>
To: <per...@li...>
Sent: Tuesday, January 09, 2001 9:50 AM
Subject: [perl-win32-gui-users] a simple question


> 
> how to set the name of a dialog box dynamically ?
> 
> $ModuleWindow = new Win32::GUI::DialogBox(
>     -title   => "old title",
>     -left    => 100,
>     -top     => 110,
>     -width   => 500,
>     -height  => 400,
>     -name    => "ModuleWindow",
>     -style   => WS_BORDER
>               | DS_MODALFRAME
>               | WS_POPUP
>               | WS_CAPTION
>               | WS_SYSMENU,
>     -exstyle => WS_EX_DLGMODALFRAME
>               | WS_EX_WINDOWEDGE
>               | WS_EX_CONTEXTHELP
>               | WS_EX_CONTROLPARENT,
> 
> );
> 
> 
> I need to do
> 
> $ModuleWindow->title("new title");
> 
> 
> 
> 
> chris
> 
> 
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Perl-Win32-GUI-Users mailing list
> Per...@li...
> http://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
> 

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

[Aldo C. <da...@pe...>]

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.
there is a small memory increase, but it's completely
acceptable (some k's when you do something in the window
at startup, click buttons, etc. but nothing when you simply
move the mouse around).

I think that the problem is in the magical stuff I've
added to support windows-as-hashes (eg. the TIEHASH stuff
that permits $Window->{-text}); since doing hv_fetch()
on a tied hash really calls the Perl sub FETCH on that
object, TMPs are really created (it seems).
hv_fetch alone would have not required a (SAVE|FREE)TMPS
block, but the magic behind it apparently does.

I will release a new version very soon with this nasty,
nasty, nasty bug finally *fixed* forever :-)

cheers,
Aldo

__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;

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

[Aldo C. <da...@pe...>]

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 :-)

> The memory usage in the task manager thingee is useful, but 
> inherently misleading. It isn't a cache allocation thing or
> anything like that, again sorry for being misleading.
>
> The problem is with the C-perl interface. The WindowMsgLoop
> needs a good perl start, and end block:
> dSP;
> ENTER;
> SAVETMPS;
>
> ....
>
> FREETMPS;
> LEAVE;

unfortunately not. WindowMsgLoop, itself, does not actually
call the Perl interpreter: the various DoEvent_* functions
performs the needed calls, and they all have (SAVE|FREE)TMPS
blocks. I tried, just to give it a try, to make the changes
you suggested to WindowMsgLoop, but nothing changes.

> This is because it calls into the perl interpreter. The Dialog
> XSUB doesn't need those blocks explicitly however because they
> are added by xsubpp. However because the Dialog XSUB pretty much
> never exits (and therefore calls FREETMPS) it accumulates TMPs. 
> There are (I believe) two ways to fix this:
> 1/ make the dialog XSUB return after processing one message, 
> and call it from perl like
> while( Win32::GUI::Dialog() ) {
> }

this is a good hint. unfortunately, it is not a solution.
there is already a one-go Dialog XSUB, which is called
DoEvents. I tried replacing the Dialog() call with this:

1 while ( Win32::GUI::DoEvents != -1 );

and indeed, there is no apparent memory leak!

BUT, the processor is busy at 100% while the Perl
program runs: this is because the while loop, even if
'void', does consume CPU time. too bad :-(

BUT, this is a first approach to a possible solution,
because it seems to isolate the problem in the Dialog()
XSUB. I'll try to debug it and see if I can understand
something more.

> 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. I implemented (1) in my copy
> of win32::GUI.

what do you mean by 'interpreter calls' here?

> NB:
> It may be necessary to add blocks in other places (in fact
> I'm sure of it), but this is the only problem I am aware of.
> I can't create and distribute a patch on work time, but in my own
> time (of which I have very little unfortunately) I will create
> a patch for 0.0.502, and send this to Aldo, if he so desires.

please do so if you can :-)


cheers,
Aldo

__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;

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

[Sam <sa...@se...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

The memory usage in the task manager thingee is useful, but 
inherently misleading. It isn't a cache allocation thing or anything 
like that, again sorry for being misleading.

The problem is with the C-perl interface. The WindowMsgLoop 
needs a good perl start, and end block:
dSP;
ENTER;
SAVETMPS;

....

FREETMPS;
LEAVE;

This is because it calls into the perl interpreter. The Dialog XSUB 
doesn't need those blocks explicitly however because they are 
added by xsubpp. However because the Dialog XSUB pretty much 
never exits (and therefore calls FREETMPS) it accumulates TMPs. 
There are (I believe) two ways to fix this:
1/ make the dialog XSUB return after processing one message, 
and call it from perl like
while( Win32::GUI::Dialog() ) {
}
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. I implemented (1) in my copy of win32::GUI.

NB:
It may be necessary to add blocks in other places (in fact I'm sure 
of it), but this is the only problem I am aware of.
I can't create and distribute a patch on work time, but in my own 
time (of which I have very little unfortunately) I will create a patch for 
0.0.502, and send this to Aldo, if he so desires.


-----BEGIN PGP SIGNATURE-----
Version: N/A

iQA/AwUBOlsd7ZsRND2Z+TaWEQLI4ACfT9k/+/Lm84a6GAhfnF8sa91kBGEAoIXP
QULIwerislw19RYsRAihlTY+
=5seU
-----END PGP SIGNATURE-----

Sam Jacobson
R & D Manager / Software Engineer
Selective Communications
Ph +64 9 302 1142
www.selective.co.nz

Re: [perl-win32-gui-users] Memory leak (not really a leak at all)

[Sam <sa...@se...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Sam wrote:
> > Hi,
> >
> > I found many references to the 'memory leak' in the archived 
> > messages at http://www.mail-archive.com/perl-win32-
> > gu...@ht.../.
> 
> > I believe there isn't a memory leak at all, it appears that the 
> > memory usage reported by windows task manager includes a 
> > portion of a windows cache allocated to the program, and that it's 
> > the cache usage that changes, not the amount of memory that the 
> > perl interpreter has allocated.
> 
> oh well, I'm really confused now :-)
> 
> > This is based on these observations:
> > 1)      As the memory usage reported by the task manager increases 
> > the total memory usage does not increase. If you run a compiler or 
> > something that will allocate memory a bit at a time for a long period 
> > of time you'll notice that as the compiler's memory usage goes up, 
> > and so does the total memory usage.
> 
> yes, this is true.
> 
> > 2)      If you minimize the perl-win32-gui app's window the reported 
> > memory usage goes down to a base value (120K with my perl), and 
> > every time you minimize the window it goes down to the same 
> > value. This is _not_ indicative of a memory leak.
> 
> this is true too.
> 
> > 3)      If you play with other applications in a similar way you
> > can make them exhibit similar behaviour. The reported memory usage
> > on other applications (my test was EditPlus) doesn't increase to 
> > the same extent, but it does increase (more on this difference later).
> 
> and this is true, but there are other applications (for example,
> the NT Task Manager) which does not exhibit this behaviour, even
> if they're left running for a large amount of time. and the Task
> Manager updates its contect each second, so is doing something.
> but its cache memory never grows up. damn :-(
> 
> > During the above I looked over the code involved, and attempted
> > to isolate a memory leak. So far as I can tell the code is rock
> > solid.
> 
> way cool ;-)
> 
> > I believe that the difference between a perl-win32-gui application, 
> > and other pure win32 applications is in the DefWindowProc 
> > handling. The perl-win32-gui module does call DefWindowProc 
> > when either you don't have a handler installed, or you return 1, 
> > however through BoundsChecker I believe that this may not always 
> > be the case.
> 
> I'm really interested in this: can you elaborate more on this
> point? do I call DefWindowProc too much, or it is not called
> when it should be?
I saw a few messages come in that weren't DefWindowProc'd, but I 
think that may have been my fault (ie returned 0 from handler).
Looking at your code it looks like DefWindowProc is called when it 
should be, but there's obviously a problem somewhere. This was a 
bit of a stab in the dark (much like the assumption about the cache 
allocation, but what other answer is there?). My next move will be 
to attempt to recreate this bug in a pure win32 app.

> > I would be interested if someone finds anything else out about
> > this problem. Unfortunately I can't spend any more time on this,
> > as it appears to me that this isn't a serious bug, at least not
> > something that will stop a program from working correctly.
> 
> well, a 4k increment for each mouse movement is quite too much,
> so something should be corrected (if it's not totally wrong, it's
> surely at least poorly coded :-)
I agree, now. There was a posting recently that reported that a perl 
gui app would crash after all available memory was consumed, so I 
will devote some of my time to fixing this problem.

I'll report when I know more.

> cheers,
> Aldo
> 
> __END__
> $_=q,just perl,,s, , another ,,s,$, hacker,,print;
> 
> 
> 
> _______________________________________________
> Perl-Win32-GUI-Users mailing list
> Per...@li...
> http://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
> 



-----BEGIN PGP SIGNATURE-----
Version: N/A

iQA/AwUBOlruq5sRND2Z+TaWEQKsowCg8YtbBZKJN7ZbK2kfuPN1ayTqKKQAoIfp
3dsqAbirf2z5dM0oe0iY+MLv
=cIST
-----END PGP SIGNATURE-----

Sam Jacobson
R & D Manager / Software Engineer
Selective Communications
Ph +64 9 302 1142
www.selective.co.nz

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

[Jeremy B. <sco...@ya...>]

If I'm not mistaken, it should be like this:

$ModuleWindow->{-title} = "New Title";

Jeremy Blonde
sco...@ya...

--- christopher sagayam <chr...@ya...>
wrote:
> 
> how to set the name of a dialog box dynamically ?
> 
> $ModuleWindow = new Win32::GUI::DialogBox(
>     -title   => "old title",
>     -left    => 100,
>     -top     => 110,
>     -width   => 500,
>     -height  => 400,
>     -name    => "ModuleWindow",
>     -style   => WS_BORDER
>               | DS_MODALFRAME
>               | WS_POPUP
>               | WS_CAPTION
>               | WS_SYSMENU,
>     -exstyle => WS_EX_DLGMODALFRAME
>               | WS_EX_WINDOWEDGE
>               | WS_EX_CONTEXTHELP
>               | WS_EX_CONTROLPARENT,
> 
> );
> 
> 
> I need to do
> 
> $ModuleWindow->title("new title");
> 
> 
> 
> 
> chris
> 
> 
> 
> 
>
_________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at
> http://mail.yahoo.com
> 
> 
> _______________________________________________
> Perl-Win32-GUI-Users mailing list
> Per...@li...
>
http://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users


__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/

Re: [perl-win32-gui-users] Memory leak (not really a leak at all)

[Aldo C. <da...@pe...>]

Sam wrote:
> Hi,
>
> I found many references to the 'memory leak' in the archived 
> messages at http://www.mail-archive.com/perl-win32-
> gu...@ht.../.

> I believe there isn't a memory leak at all, it appears that the 
> memory usage reported by windows task manager includes a 
> portion of a windows cache allocated to the program, and that it's 
> the cache usage that changes, not the amount of memory that the 
> perl interpreter has allocated.

oh well, I'm really confused now :-)

> This is based on these observations:
> 1)      As the memory usage reported by the task manager increases 
> the total memory usage does not increase. If you run a compiler or 
> something that will allocate memory a bit at a time for a long period 
> of time you'll notice that as the compiler's memory usage goes up, 
> and so does the total memory usage.

yes, this is true.

> 2)      If you minimize the perl-win32-gui app's window the reported 
> memory usage goes down to a base value (120K with my perl), and 
> every time you minimize the window it goes down to the same 
> value. This is _not_ indicative of a memory leak.

this is true too.

> 3)      If you play with other applications in a similar way you
> can make them exhibit similar behaviour. The reported memory usage
> on other applications (my test was EditPlus) doesn't increase to 
> the same extent, but it does increase (more on this difference later).

and this is true, but there are other applications (for example,
the NT Task Manager) which does not exhibit this behaviour, even
if they're left running for a large amount of time. and the Task
Manager updates its contect each second, so is doing something.
but its cache memory never grows up. damn :-(

> During the above I looked over the code involved, and attempted
> to isolate a memory leak. So far as I can tell the code is rock
> solid.

way cool ;-)

> I believe that the difference between a perl-win32-gui application, 
> and other pure win32 applications is in the DefWindowProc 
> handling. The perl-win32-gui module does call DefWindowProc 
> when either you don't have a handler installed, or you return 1, 
> however through BoundsChecker I believe that this may not always 
> be the case.

I'm really interested in this: can you elaborate more on this
point? do I call DefWindowProc too much, or it is not called
when it should be?

> I would be interested if someone finds anything else out about
> this problem. Unfortunately I can't spend any more time on this,
> as it appears to me that this isn't a serious bug, at least not
> something that will stop a program from working correctly.

well, a 4k increment for each mouse movement is quite too much,
so something should be corrected (if it's not totally wrong, it's
surely at least poorly coded :-)

cheers,
Aldo

__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;

RE: [perl-win32-gui-users] Listbox or Combobox style options

[Joel O. <a94...@du...>]

Done... I just RTFM and the FAQs and I found the answer. _:)
Thanks all.

	Joel Oliveira

--------------------------------------------

# -----Original Message-----
# From: per...@li...
# [mailto:per...@li...]On Behalf Of
# Joel Oliveira
# Sent: terca-feira, 9 de Janeiro de 2001 12:56
# To: per...@li...
# Subject: [perl-win32-gui-users] Listbox or Combobox style options
# 
# 
# Hello all,
# 
# I need a listbox similar to the HTML one. Read only, only one 
# selection and
# with a "drop list with vscroll".
# I tried the next code, but a can't get the "drop" style to work...
# $WD->AddListbox(-text=>'&Month',-name=>'Month',-left=>106,-top=>88
# ,-width=>6
# 5,-height=>20,-multisel=>0,-style=>WS_VISIBLE|WS_VSCROLL);
# 
# 
# 	Joel Oliveira
# 
# --------------------------------------------
# 
# 
# _______________________________________________
# Perl-Win32-GUI-Users mailing list
# Per...@li...
# http://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
# 

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

[christopher s. <chr...@ya...>]

how to set the name of a dialog box dynamically ?

$ModuleWindow = new Win32::GUI::DialogBox(
    -title   => "old title",
    -left    => 100,
    -top     => 110,
    -width   => 500,
    -height  => 400,
    -name    => "ModuleWindow",
    -style   => WS_BORDER
              | DS_MODALFRAME
              | WS_POPUP
              | WS_CAPTION
              | WS_SYSMENU,
    -exstyle => WS_EX_DLGMODALFRAME
              | WS_EX_WINDOWEDGE
              | WS_EX_CONTEXTHELP
              | WS_EX_CONTROLPARENT,

);


I need to do

$ModuleWindow->title("new title");




chris




_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[perl-win32-gui-users] Listbox or Combobox style options

[Joel O. <a94...@du...>]

Hello all,

I need a listbox similar to the HTML one. Read only, only one selection and
with a "drop list with vscroll".
I tried the next code, but a can't get the "drop" style to work...
$WD->AddListbox(-text=>'&Month',-name=>'Month',-left=>106,-top=>88,-width=>6
5,-height=>20,-multisel=>0,-style=>WS_VISIBLE|WS_VSCROLL);


	Joel Oliveira

--------------------------------------------

[perl-win32-gui-users] Re: [perl-win32-gui] Event processing

[Eric B. <er...@eb...>]

On Wed, 3 Jan 2001, Robert Sherman wrote:

> sub Loop_Click {
> 	while ($i<20) {
> 		sleep 1;
> 		if ($i==10){
> 			&Show_Win2($i);
>    			}
> 		$i++;
> 		}
> }

One way to do this is to use a timer:


# Warning: Untested code

my $loop_counter;
my $LoopTimer = Window->AddTimer("LoopTimer", 0);

sub Loop_Click {
   $loop_counter = 0;
   $LoopTimer->Interval( 1000 );
      # Use a short interval if all you want is event procesing.
      # Here the 1000ms interval substitutes for your sleep 1.
}

sub LoopTimer_Timer {
   &Show_Win2( $loop_counter )  if $loop_counter == 10;
   ++$loop_counter;
   $LoopTimer->Kill() if $loop_counter >= 20;
}


If you have a lot of loop state and you don't want it all at file level
you can also use a closure.  This has a side effect of making the timer
generic.


# Warning: Untested code

my $loop_body;
my $LoopTimer = Window->AddTimer("LoopTimer", 0);

sub Loop_Click {
   my $loop_counter = 0;

   $loop_body = sub {
      &Show_Win2( $loop_counter )  if $loop_counter == 10;
      ++$loop_counter;
      $LoopTimer->Kill() if $loop_counter >= 20;
   }

   $LoopTimer->Interval( 1000 );
}

sub LoopTimer_Timer {
    $loop_body->();
}


This could be done very nicely with perl-level threads. (i.e. one at a
time but with multiple call stacks where one could pass control to
another)

   - Eric B.

--
"An intelligent carrot!  It boggles the mind."

Re: [perl-win32-gui-users] cygwin (was newbie query)

[Aldo C. <da...@pe...>]

Aldo Calpini wrote:
> I am also trying to fool around with cygwin, but I didn't
> even could produce a working Perl build :-(

well, I finally solved the problem, it was really a WKP
(Well Known Problem :-).
if anybody it's interested, the solution is available at:

http://sources.redhat.com/ml/cygwin/2000-08/msg00256.html

you need to download dll_entry.o, then do:

    ar cru /usr/lib/libcygwin.a dll_entry.o
    ranlib /usr/lib/libcygwin.a

then rebuild perl, and everything goes smooth :-)

I'll try to work on porting Win32::GUI under GCC (if time
permits).


cheers,
Aldo

__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;

Re: [perl-win32-gui-users] Memory leak (not really a leak at all)

[Reini U. <ru...@sb...>]

Have you tried Devel::Leak ?

It works better with a -DDEBUGGING perl version which I currently 
don't have for MSVC.

Sam wrote:
> I believe there isn't a memory leak at all, it appears that the
> memory usage reported by windows task manager includes a
> portion of a windows cache allocated to the program, and that it's
> the cache usage that changes, not the amount of memory that the
> perl interpreter has allocated.
>
> During the above I looked over the code involved, and attempted to
> isolate a memory leak. So far as I can tell the code is rock solid.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/autocad/news/faq/autolisp.html

[perl-win32-gui-users] URL Link Object?

[<tim...@lm...>]

Aldo or anyone else-

Is there an object within Win32::GUI that will allow you to have a URL =
link in a GUI-window? When you click on the text it should open up your =
default browser and take you to that URL. You know, the kind that a lot =
of Apps have in their About screen. Or is there another way to create =
this effect?

        Thanks,

                Tim Thomas





------------------------------------------------------------------------=
-------------------------
Tim Thomas
Unix Systems Administrator
Lockheed Martin EIS =B7 Denver Data Center
303-430-2281
mailto:tim...@lm... <mailto:tim...@lm...>=20
------------------------------------------------------------------------=
-------------------------

RE: [perl-win32-gui-users] Memory leak (not really a leak at all)

[<Chr...@ti...>]

I know from personal experience that there is a memory handling problem in
win32-gui.  

I had an application that could be turned on or put into "pause" mode -
which meant it would not do any processing until the start button was
clicked.  This application would drag any computer I put it on to a halt.
The time it took to do this depended on how much memory the machine had to
start with.  

It seems to me that if this problem only concerned windows cache allocation,
that it would not make the box grind to a halt.

I will admit that I do not understand the intricacies of how windows handles
memory, but I did want to add my personal experiences in hopes it may shed
light  on the problems.

HTH,
tcl...@we...    

-----Original Message-----
From: Sam [mailto:sa...@se...]
Sent: Sunday, January 07, 2001 9:32 PM
To: per...@ht...
Subject: [perl-win32-gui-users] Memory leak (not really a leak at all)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I found many references to the 'memory leak' in the archived 
messages at http://www.mail-archive.com/perl-win32-
gu...@ht.../.

I believe there isn't a memory leak at all, it appears that the 
memory usage reported by windows task manager includes a 
portion of a windows cache allocated to the program, and that it's 
the cache usage that changes, not the amount of memory that the 
perl interpreter has allocated.
This is based on these observations:
1)	As the memory usage reported by the task manager increases 
the total memory usage does not increase. If you run a compiler or 
something that will allocate memory a bit at a time for a long period 
of time you'll notice that as the compiler's memory usage goes up, 
and so does the total memory usage.
2)	If you minimize the perl-win32-gui app's window the reported 
memory usage goes down to a base value (120K with my perl), and 
every time you minimize the window it goes down to the same 
value. This is _not_ indicative of a memory leak.
3)	If you play with other applications in a similar way you can 
make them exhibit similar behaviour. The reported memory usage 
on other applications (my test was EditPlus) doesn't increase to 
the same extent, but it does increase (more on this difference later).

During the above I looked over the code involved, and attempted to 
isolate a memory leak. So far as I can tell the code is rock solid.


I believe that the difference between a perl-win32-gui application, 
and other pure win32 applications is in the DefWindowProc 
handling. The perl-win32-gui module does call DefWindowProc 
when either you don't have a handler installed, or you return 1, 
however through BoundsChecker I believe that this may not always 
be the case.

I would be interested if someone finds anything else out about this 
problem. Unfortunately I can't spend any more time on this, as it 
appears to me that this isn't a serious bug, at least not something 
that will stop a program from working correctly.



-----BEGIN PGP SIGNATURE-----
Version: N/A

iQA/AwUBOliL8ZsRND2Z+TaWEQJGwgCeMkadt3YnnIh+sC3In8ZbMObH3WkAoPLK
qIBjQIZHm48LYi6tlAehlC+G
=u9/m
-----END PGP SIGNATURE-----

Sam Jacobson
R & D Manager / Software Engineer
Selective Communications
Ph +64 9 302 1142
www.selective.co.nz

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

Re: [perl-win32-gui-users] newbie - trying to get data from text box

[Jonathan S. <jso...@al...>]

FW: [perl-win32-gui-users] newbie - trying to get data from text boxYes =
that is also possible.  Try this:

To set the cursor in the textfield:=20
$Frame->aTextField->SetFocus();

Jonathan Southwick
Technical & Network Services
Allegheny College, Meadville, PA
jso...@al...



----- Original Message -----=20
  From: Michael Solomon=20
  To: Perl Gui (E-mail)=20
  Sent: Monday, January 08, 2001 6:55 AM
  Subject: FW: [perl-win32-gui-users] newbie - trying to get data from =
text box


  Thanks for this=20

  I can now capture the text=20

  What I would also like to do is start with the cursor in the text box =
rather than having to click on it.=20

  Is that possible and if so how do I do it=20



  Regards=20



  Mike Solomon=20



  -----Original Message-----=20
  From:   Anthony C. George [mailto:ag...@em...]=20
  Sent:   05 January 2001 18:46=20
  To:     per...@li...=20
  Subject:        RE: [perl-win32-gui-users] newbie - trying to get data =
from text box=20

  To get the text in the box:=20
  $myText=3D$Frame->aTextField->Text();=20
  To set the text:=20
  $Frame->aTextField->Text($myText);=20



  >tony=20

  -----Original Message-----=20
  From:   per...@li...=20
  [mailto:per...@li...]On Behalf Of=20
          Michael Solomon=20
  Sent:   Friday, January 05, 2001 11:18 AM=20
  To:     Perl Gui (E-mail)=20
  Subject:        [perl-win32-gui-users] newbie - trying to get data =
from text box=20



  I have just started looking at Win32 Gui=20
  What I want to do is put up a text box and allow a user to enter data =
then=20
  capture it=20
  By looking at code posted here I have written the following: use =
Win32::GUI;=20
  $Frame =3D new Win32::GUI::Window(=20
  * name =3D> "aFrame",=20
  * top =3D> 100,=20
  * left =3D> 150,=20
  * width =3D> 350,=20
  * height =3D> 200,=20
  * title =3D> "Test Win32::GUI",=20
              );=20
  $Frame->AddTextfield(=20
  * name =3D> "aTextField",=20
  * top =3D> 50,=20
  * left =3D> 20,=20
  * height =3D> 20,=20
  * width =3D> 300,=20
  * prompt =3D> "Type a text here : ",=20
             );=20
  $Frame->AddButton(=20
  * name =3D> "aButton",=20
  * text =3D> "OK",=20
  * top =3D> 90,=20
  * left =3D> 150,=20
  * height =3D> 25=20
  * width =3D> 50,=20
                 );=20

  $Frame->Show();=20
  Win32::GUI::Dialog();=20
  sub aFrame_Terminate {=20
  * 1;=20
            }=20

  sub aButton_Click {=20
  print "test\n";=20
  &aFrame_Terminate;=20
  }=20



  What I haven't worked out how to do is to access the text entered.  =
Also I want the cursor to start in the text box rather than having to =
click on it.

  Any help will be gratefully received.=20
  Regards=20

  Mike Solomon=20
  Technical Manager=20
  Work     01582 831125=20
  Mobile 07941 537 172=20
  email   mso...@3s...=20
  =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=20
  =3D=3D=3D=3D=3D=20
  Important: Any views or opinions expressed by the sender do not =
necessarily=20
  represent those of the 3s Group. This e-mail and any attachment(s)=20
  are intended for the above named only and may be confidential.  If you =
are=20
  not=20
  the named recipient please notify us immediately.  You must not copy =
or=20
  disclose=20
  the contents to any third party.=20
  Internet e-mail is not a fully secure communications medium.  Please =
take=20
  this into account when sending e-mail to us.=20
  Any attachment(s) to this e-mail are believed to be free from virus, =
but it=20
  is the responsibility of the recipient to make all the necessary virus =

  checks.=20
  www.3s-group.com=20
  =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20




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

FW: [perl-win32-gui-users] newbie - trying to get data from text box

[Michael S. <MSo...@3s...>]

Thanks for this

I can now capture the text

What I would also like to do is start with the cursor in the text box rather
than having to click on it.

Is that possible and if so how do I do it


Regards


Mike Solomon


-----Original Message-----
From:	Anthony C. George [mailto:ag...@em...] 
Sent:	05 January 2001 18:46
To:	per...@li...
Subject:	RE: [perl-win32-gui-users] newbie - trying to get data from
text box

To get the text in the box:
$myText=$Frame->aTextField->Text();
To set the text:
$Frame->aTextField->Text($myText);


>tony

-----Original Message-----
From:	per...@li...
[mailto:per...@li...]On Behalf Of
	Michael Solomon
Sent:	Friday, January 05, 2001 11:18 AM
To:	Perl Gui (E-mail)
Subject:	[perl-win32-gui-users] newbie - trying to get data from text
box


I have just started looking at Win32 Gui
What I want to do is put up a text box and allow a user to enter data then
capture it
By looking at code posted here I have written the following: use Win32::GUI;
$Frame = new Win32::GUI::Window(
* name => "aFrame",
* top => 100,
* left => 150,
* width => 350,
* height => 200,
* title => "Test Win32::GUI",
            );
$Frame->AddTextfield(
* name => "aTextField",
* top => 50,
* left => 20,
* height => 20,
* width => 300,
* prompt => "Type a text here : ",
           );
$Frame->AddButton(
* name => "aButton",
* text => "OK",
* top => 90,
* left => 150,
* height => 25
* width => 50,
               );

$Frame->Show();
Win32::GUI::Dialog();
sub aFrame_Terminate {
* 1;
          }

sub aButton_Click {
print "test\n";
&aFrame_Terminate;
}


What I haven't worked out how to do is to access the text entered.  Also I
want the cursor to start in the text box rather than having to click on it.
Any help will be gratefully received.
Regards

Mike Solomon
Technical Manager
Work     01582 831125
Mobile 07941 537 172
email   mso...@3s...
===========================================================================
=====
Important: Any views or opinions expressed by the sender do not necessarily
represent those of the 3s Group. This e-mail and any attachment(s)
are intended for the above named only and may be confidential.  If you are
not
the named recipient please notify us immediately.  You must not copy or
disclose
the contents to any third party.
Internet e-mail is not a fully secure communications medium.  Please take
this into account when sending e-mail to us.
Any attachment(s) to this e-mail are believed to be free from virus, but it
is the responsibility of the recipient to make all the necessary virus
checks.
www.3s-group.com
========================================================================



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

Re: [perl-win32-gui-users] Re: [perl-win32-gui] newbie query

[Aldo C. <da...@pe...>]

Reini Urban wrote:
> Aldo,
> i'm still trying to fool around with cygwin and mingw,
> but at first have to build a new mingw-perl 5.6.1, because with
> this it will be much easier. (it can use the msvc headers and
> libs, and not the cygwin/w32api)
> but at first I have the solve the current cygwin perl-5.6.1-1
> problem with gdbm.

I am also trying to fool around with cygwin, but I didn't
even could produce a working Perl build :-(
I'm trying to build the Perl 5.6.0 source tree under a
precompiled cygwin install, and it seems everything goes
well, I have a perl.exe but everytime it is launched it
says that the application failed to initialize properly
(0xc0000005). should be something stupid like access denied
to some shared library, but I can't track it down.
BTW, I gave libmsvcrt.a to Configure when it was asking for
my C library, dunno if it's correct...

PS. this thread should probably be moved to the
Perl-Win32-GUI-Hackers mailing list ;-)


cheers,
Aldo

__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;

[perl-win32-gui-users] Memory leak (not really a leak at all)

[Sam <sa...@se...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I found many references to the 'memory leak' in the archived 
messages at http://www.mail-archive.com/perl-win32-
gu...@ht.../.

I believe there isn't a memory leak at all, it appears that the 
memory usage reported by windows task manager includes a 
portion of a windows cache allocated to the program, and that it's 
the cache usage that changes, not the amount of memory that the 
perl interpreter has allocated.
This is based on these observations:
1)	As the memory usage reported by the task manager increases 
the total memory usage does not increase. If you run a compiler or 
something that will allocate memory a bit at a time for a long period 
of time you'll notice that as the compiler's memory usage goes up, 
and so does the total memory usage.
2)	If you minimize the perl-win32-gui app's window the reported 
memory usage goes down to a base value (120K with my perl), and 
every time you minimize the window it goes down to the same 
value. This is _not_ indicative of a memory leak.
3)	If you play with other applications in a similar way you can 
make them exhibit similar behaviour. The reported memory usage 
on other applications (my test was EditPlus) doesn't increase to 
the same extent, but it does increase (more on this difference later).

During the above I looked over the code involved, and attempted to 
isolate a memory leak. So far as I can tell the code is rock solid.


I believe that the difference between a perl-win32-gui application, 
and other pure win32 applications is in the DefWindowProc 
handling. The perl-win32-gui module does call DefWindowProc 
when either you don't have a handler installed, or you return 1, 
however through BoundsChecker I believe that this may not always 
be the case.

I would be interested if someone finds anything else out about this 
problem. Unfortunately I can't spend any more time on this, as it 
appears to me that this isn't a serious bug, at least not something 
that will stop a program from working correctly.



-----BEGIN PGP SIGNATURE-----
Version: N/A

iQA/AwUBOliL8ZsRND2Z+TaWEQJGwgCeMkadt3YnnIh+sC3In8ZbMObH3WkAoPLK
qIBjQIZHm48LYi6tlAehlC+G
=u9/m
-----END PGP SIGNATURE-----

Sam Jacobson
R & D Manager / Software Engineer
Selective Communications
Ph +64 9 302 1142
www.selective.co.nz

[perl-win32-gui-users] RE: [perl-win32-gui] Print

[Peter E. <Pet...@at...>]

True. But when I do this, I still don't get that option.

-----Original Message-----
From: MATA Tech [mailto:ma...@ma...]
Sent: Thursday, January 04, 2001 12:13 PM
To: per...@ht...
Subject: Re: [perl-win32-gui] Print


Peter:

As I understand it, you must highlight a selection to enable that 
radio button.  Otherwise, it is assumed that the user wants to print 
the entire portion.  

B Smith


On 26 Dec 00, at 17:19, Peter Eisengrein wrote:

> I saw a previous posting about using system("rundll32.exe
> $dll,PrintHTML $tmpfile"); to print a file and it works well for my
> app. However, I'd like to be able to "print selection" That radio
> button is currently disabled. Anyone know what variable to set to tell
> the system that you have selected some text in a AddRichEdit field?
> 
> Thanks,
> Pete
> 

RE: [perl-win32-gui-users] menu

[Peter E. <Pet...@at...>]

I tested your code and could see the menu. WHat versions of perl and
Win32-GUI are you using?

-----Original Message-----
From: Koul Christian [mailto:chr...@fu...]
Sent: Friday, January 05, 2001 6:45 AM
To: per...@ht...
Subject: [perl-win32-gui-users] menu


Hi,

    I am new in win32::GUI and i have problem using menu.
I have this but i can not see the menu. can somebody help me?

-------------------------------------------
use Win32::GUI;

    $Menu =3D new Win32::GUI::Menu(
                  "&File"    =3D> "File",
                  " > &Load" =3D> "FileLoad",
             );

    $Frame =3D new Win32::GUI::Window(
          -name =3D> "aFrame",
          -top =3D> 100,
          -left =3D> 150,
          -width =3D> 350,
          -height =3D> 400,
          -title =3D> "Test Win32::GUI",
          -menu =3D> $Menu,
         );
    $Frame->AddTextfield(
             -name =3D> "aTextField",
              -top =3D> 200,
              -left =3D> 20,
              -height =3D> 20,
              -width =3D> 300,
             -prompt =3D> "Type a text here : ",
        );
      $Frame->AddButton(
          -name =3D> "aButton",
          -text =3D> "OK",
          -top =3D> 260,
          -left =3D> 150,
          -height =3D> 25
          -width =3D> 50,
         );

    $Frame->AddStatusBar();
    $Frame->Show();

    Win32::GUI::Dialog();

    sub aFrame_Terminate {
         -1;
    }

-------------------------------------------


--

Sincerely.
__________________

Christian Koul
Civil Engineer
Unit=E9 Statistique - Fucam



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

[perl-win32-gui-users] NT/98 incompatibilities?

[Peter E. <Pet...@at...>]

I have a script that reads a file (puts the data into @update) and prints it
to a RichEdit window. This works well on NT but I am having problems with it
on Win98.

As it is being written to the Rich Edit field, the scroll bar starts out
large and scales smaller as more is added (as expected). However,
occassionally on 98 the scroll bar "bounces" back to large and begins
scaling again. When this happens, data is lost as if a buffer fills up and
then gets dumped FIFO. Again, this is not an issue on NT.

Anyone seen anything like this?

I am updating the RichEdit as follows:

push(@update,$line);
$Window->Editor->Text($Window->Editor->Text . join("", @update));

There is regex that determines when @update gets undef'd. I am doing it this
way because only some of this info gets written to a different window
("filter" window).

Any help would be greatly appreciated!!!
-Pete

Re: [perl-win32-gui-users] Re: [perl-win32-gui] newbie query

[Reini U. <ru...@sb...>]

Aldo Calpini wrote:
> it should be possible to use cygwin's gcc but I haven't played with it
> very much. if you want to test it, you're very welcome.
> you need to download the Perl source and compile it under your
> cygwin environment, then try to compile the module.

Aldo,
i'm still trying to fool around with cygwin and mingw,
but at first have to build a new mingw-perl 5.6.1, because with this 
it will be much easier. (it can use the msvc headers and libs, and 
not the cygwin/w32api)
but at first I have the solve the current cygwin perl-5.6.1-1 problem with
gdbm.

some notes:
ctl3d.h will not work.
I added a lot of PL_ prefixes so far, but it's still not ready.
gcc is MUCH stricter than cl, it barfs with a lot of errors so far.
and some constants are still not defined in the cygwin w32api.

sample:
GUI.xs: In function `void DrawSplitter(HWND__ *)':
GUI.xs:734: ANSI C++ forbids implicit conversion from `void *' in assignment
GUI.xs:735: ANSI C++ forbids implicit conversion from `void *' in assignment
GUI.xs: In function `LRESULT InteractiveGraphicMsgLoop(HWND__ *, unsigned int,
u
nsigned int, long int)':
GUI.xs:1710: warning: negative value `-1' passed as argument 3 of
`PostMessageA(
HWND__ *, unsigned int, unsigned int, long int)'
GUI.xs: In function `LRESULT WindowMsgLoop(HWND__ *, unsigned int, unsigned
int,
 long int)':
GUI.xs:1829: warning: NULL used in arithmetic
GUI.xs:1843: warning: NULL used in arithmetic
GUI.xs:2646: warning: NULL used in arithmetic
GUI.xs:2676: warning: negative value `-1' passed as argument 3 of
`PostMessageA(
HWND__ *, unsigned int, unsigned int, long int)'
GUI.xs: In function `LRESULT MsgLoop(HWND__ *, unsigned int, unsigned int,
long
int)':
GUI.xs:2724: warning: NULL used in arithmetic
GUI.xs:2794: warning: negative value `-1' passed as argument 3 of
`PostMessageA(
HWND__ *, unsigned int, unsigned int, long int)'
GUI.xs: In function `void ParseWindowOptions(SV **, SV **, long int, long int,
i
nt, tagPERLCREATESTRUCT *)':
GUI.xs:3100: `SS_PATHELLIPSIS' undeclared (first use this function)
GUI.xs:3101: `SS_ENDELLIPSIS' undeclared (first use this function)
...
-- 
Reini Urban
http://xarch.tu-graz.ac.at/autocad/news/faq/autolisp.html