RE: [perl-win32-gui-hackers] Proposition for NEM

2003-12-05 Thread Stephen Pick
Hi Aldo, >1) you can't easily (I mean, without a lot of effort) intercept all > kind of messages. I'm aware of this. Currently this is not meant as a simplicity feature; the NEM does that already. It's meant as something for people who know what they're doing when the NEM won't do, so they can

[perl-win32-gui-hackers] DoEvents() bug.

2003-12-09 Thread Stephen Pick
Hi all. When I do this: Win32::GUI::Dialog() I receive all my events like WM_LBUTTONDOWN (-onMouseDown) once, as should happen. When I do this: while(1) { Win32::GUI::DoEvents() print "Loop!\n"; } I get endless calls to my event handler so long as the mouse button is down. I h

RE: [perl-win32-gui-hackers] DoEvents() bug.

2003-12-10 Thread Stephen Pick
I can find a way to solve the problem. Steve -Original Message- From: Glenn Linderman [mailto:[EMAIL PROTECTED] Sent: 09 December 2003 19:03 To: Stephen Pick Cc: Win32 GUI Hackers Subject: Re: [perl-win32-gui-hackers] DoEvents() bug. On approximately 12/9/2003 2:59 AM, came the following

[perl-win32-gui-hackers] "Fix": DoEvents() bug.

2003-12-10 Thread Stephen Pick
Hi. OK. This is probably the strangest and most baffling fix I could have stumbled on for this bug but here goes: IO flushing. Yep. If you flush *any* filehandle currently open for writing (by whatever means you like) immediately after calling Win32::GUI::DoEvents, you don't get repeated message

[perl-win32-gui-hackers] Mini update to Hook()

2003-12-11 Thread Stephen Pick
Hi, Just thought I'd add a little something to the HEM (Hacker/Horrible/Hotchpotch Event Model). $win->Hook() now returns the previous coderef if you reassign a hook. For instance: my $hookone = $win->Hook(0x0020, \&setcursor); my $hooktwo = $win->Hook(0x0020, \&somethingelse); $hookone now eq

RE: [perl-win32-gui-hackers] bugfixed some cvs

2003-12-16 Thread Stephen Pick
Hi, The problem is simply that the implementation of relative co-ordinates is not done properly. If you make a parent window and give it a child window that is a DialogBox, then position the main window at screen co-ordinates 100x100, then call $CHILD->Top(0); to position child window at the

RE: [perl-win32-gui-hackers] bugfixed some cvs

2003-12-17 Thread Stephen Pick
EMAIL PROTECTED] Sent: 16 December 2003 19:13 To: Stephen Pick Cc: Win32 GUI Hackers Subject: Re: [perl-win32-gui-hackers] bugfixed some cvs OK, i understand your problem now. I agree Main window and Dialog box have screen coordinate. Dialog box have a parent window but it's not a child

RE: [perl-win32-gui-hackers] -noflicker Feedback/bugs

2003-12-17 Thread Stephen Pick
Yes yes yes. As was posted in the mail regarding the -noflicker option, as was written in the documentation for the noflicker option, and as was noted in the changelog for the noflicker option: IT BREAKS STUFF. If it didnt, it wouldnt be an option. I'm gratified to see that most of the stuff

RE: [perl-win32-gui-hackers] -noflicker Feedback/bugs

2003-12-17 Thread Stephen Pick
ut just why that particular control isn't drawing right. One hopes that WM_PRINT is implemented there. 23 windows?! Steve -Original Message- From: Jez White [mailto:[EMAIL PROTECTED] Sent: 17 December 2003 11:53 To: Stephen Pick; guihackers Subject: Re: [perl-win32-gui-hackers]

[perl-win32-gui-hackers] Which CVS branch are we supposed to use?

2004-01-05 Thread Stephen Pick
Hi, Now there's a CVS branch for 670 and 665-Fix. Which one are we meant to commit to? Which one contains the latest code? Shouldn't we make the 670 branch the one we're all meant to commit to now? Steve

[perl-win32-gui-hackers] Millions of constants

2004-01-07 Thread Stephen Pick
Hi, I've identified about 4000 constants from CommCtl.h and WinUser.h that are not exported by Win32::GUI. I've autogenerated a GUI_Constants.cpp but I'm reluctant to add it to the current CVS as it seems like an incredible bloat. Perhaps this absolutely huge list of constants could be a suppo

[perl-win32-gui-hackers] Some modifications to GUI_MessageLoops.cpp

2004-01-13 Thread Stephen Pick
Hi all, Glenn Munroe pointed out that when you return a value from a handler it is discarded by Win32::GUI. Some notify messages and other messages benefit from the ability to return a specific result from the wndproc. I've implemented this as follows: In your handler, if you want to explicitly

RE: [perl-win32-gui-hackers] notta lotta

2004-02-03 Thread Stephen Pick
Perhaps the silence is due to me being away for a week ;) I'm back now, ready to fix stuff once more, though churning through all the messages on the Users list is a bit of a pain. I think we should do another release. I see no reason not to, especially now that SourceForge seems to be behaving i

RE: [perl-win32-gui-hackers] Strange behaviour in the NEM - Bugs?

2004-02-16 Thread Stephen Pick
Whoa PMX is shoddy. I got the message you mentioned when I first tried it, but after that I get "Memory could not be 'read'" at 0x000. If I disable all the NEM stuff and then go to the about screen, when I click OK the program locks up. I'm looking into the crash out of curiosity. If some

[perl-win32-gui-hackers] safemalloc() not safe?

2004-02-16 Thread Stephen Pick
Hi, Firstly - what on earth is safemalloc()? It seems to be documented in old patches to the perl 5.005 API, but not since then. Secondly - safemalloc() seems to fail when reserving space for text label strings in the InsertItem function of TreeView.xs. The samples/pmx.pl file distributed with

Addition: [perl-win32-gui-hackers] safemalloc() not safe?

2004-02-16 Thread Stephen Pick
Regular malloc seems to fail too. This is now really confusing. Steve > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Behalf Of > Stephen Pick > Sent: 16 February 2004 12:14 > To: Win32 GUI Hackers (E-mail) > Subject: [perl-win32

[perl-win32-gui-hackers] Menus and NEM

2004-02-16 Thread Stephen Pick
Hello, Looks like menus are indeed a little busted. You can't use both event models on a menu. You can use either the NEM or the OEM, but you can't selectively use NEM here and OEM there. If you add a menu to a window that is using the NEM and your window uses OEM, your menu won't work. Your me

[perl-win32-gui-hackers] CVS update: Toolbars

2004-02-17 Thread Stephen Pick
Hi, I've just spent the morning converting and documenting Rammy's perl toolbar functions into XS. They're now in the CVS. The new functions are as follows: # (@)METHOD:SetButtonState(BUTTON, STATE) # (@)METHOD:SetStyle(STYLE) # (@)METHOD:SetExtendedStyle(STYLE) # (@)METHOD:GetStyle(STYLE) # (@)

RE: [perl-win32-gui-hackers] CVS update: Toolbars

2004-02-18 Thread Stephen Pick
Yep, it will shift down to the bottom when you do SetStyle because you're replacing the styles. The common control style CCS_TOP is applied by default on new toolbars, but as soon as you do SetStyle you remove this style unless you explicitly add it into your setstyle call. CCS_TOP is defined a

Addition: [perl-win32-gui-hackers] CVS update: Toolbars

2004-02-18 Thread Stephen Pick
To enable tooltips you need to do something like this: $TB->SetStyle(TBSTYLE_FLAT|TBSTYLE_TRANSPARENT|1|TBSTYLE_LIST|TBSTYLE_TOOLTIPS); $TB->SetExtendedStyle(0x0008); 0x0008 is the TBSTYLE_EX_MIXEDBUTTONS style which is only compiled in if the constant _WIN32_IE is greater or equal to 0x0

[perl-win32-gui-hackers] COMMIT: [perl-win32-gui-users] Shipping resources with your exe

2004-02-19 Thread Stephen Pick
Goody Gumdrops. Just committed a change to CVS so that icons, bitmaps and cursors created in the standard way are first checked for in the EXE file that loaded Win32::GUI. Now there are some little points of note: 1. Doesnt work with PAR (unless you're a sneaky bugger). The reason it doesnt

RE: [perl-win32-gui-hackers] Menus and NEM

2004-02-24 Thread Stephen Pick
labels, buttons etc support Japanese characters under Win32::GUI provided that your OS language is set to Japanese (_that_ was a disorienting few hours (no pun intended :/)...). This is true of XP as well. Steve > -Original Message- > From: Glenn Linderman [mailto:[EMAIL PROTECTED] &