Win32::API caveat

Another thing I've just discovered is that you cannot wrap

        Win32::API::->Import(
            "user32",
            "DWORD GetWindowThreadProcessId( HWND hWnd, LPDWORD lpdwPr
+ocessId)"
        ) or die $^E;
[download]

in a begin block. If you do, it won't work properly. For example if you tried GetWindowThreadProcessId($handle, $procid); $procid would not be populated with the process id as is expected. This drove me crazy 10min ago.

update: also, be sure the new parent window has wxCLIP_CHILDREN on, otherwise flicker galore

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Comment on Win32::API caveat Select or Download Code

Replies are listed 'Best First'.
Re: Win32::API caveat by blackadder (Hermit) on May 14, 2004 at 11:50 UTC
I am completely Lost now,.... Blackadder	[reply]
Re: Re: Win32::API caveat by blackadder (Hermit) on May 14, 2004 at 12:43 UTC
Oh yes,clear as mud,..are you showing off???? Damn! losing points and still don't understand this scribbles. surely there is something more simpler form me to understand that all this examplish thing....surely!!!!!!! Thanks anyway. Blackadder	[reply]

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.