On approximately 10/2/2004 8:20 AM, came the following characters from
the keyboard of Laurent ROCHER:
Hi Win32::GUI users,
A new version 0.99_1 of Win32::GUI is availlable at Sourceforge.
This is first Release candidate for Win32::GUI 1.0.
Please try it, and report any problem
>
> Not something we should hold up the release for; seeing as there seems
> to be a new release, I guess Laurent agreed on that point!
>
I agree, i just finish upload Win32::GUI 0.99_1 at sourceforge :)
Laurent
Hi Win32::GUI users,
A new version 0.99_1 of Win32::GUI is availlable at Sourceforge.
This is first Release candidate for Win32::GUI 1.0.
This version come from main developpement branch of Win32::GUI.
- Completely new base code.
- Full NEM/OEM support.
- L
On approximately 10/2/2004 6:17 AM, came the following characters from
the keyboard of Jez White:
It would be nice to be able to create dynamic auto destroying menus
too:) You could then create menus based upon dynamic contexts, without
worrying about memory leaks. I had a look at implementing
Thanks, Laurent for the explanation. I think you got your point across. I
was unaware of the implications of your new window destruction.
I would put money on that your bug is related to what Laurent suggested,
I've been bitten twice by similar things.
So I don't know if there's any "good" s
It seems (confirm this if you can Jez) that the "issues" probably only
occur for SB_THUMBPOSITION and SB_THUMBTRACK operations, as these are
the only that use the position value which is potentially from the
WM_HSCROLL or WM_VSCROLL message.
To allow easier "plumbing", and for the sake of effi
Hi,
I prepare all for made a 0.99_1 release for a first 1.0 release
candidate.
I publish it on sourceforge and try to publish it on CPAN too.
Laurent
>
> Is there anything else stopping us from making Win32::GUI 1.0.0 ? And
> putting it on CPAN, even, if you have that figured out?
>
7 matches
Mail list logo
