From: Glenn L. <pe...@ne...> - 2003-11-06 07:56:15
|
Hi, It was extremely important for my next project that I have accelerator keys working in Win32::GUI (or whatever interface I chose to code to). As it turns out, there were only a few scattered places to fix things, and I was able to get them working. However, along the way, for debugging purposes (debugging several things, see ** below), I have changed or rearranged a fair number of lines of code in a few of the source files. Hence, it is not particularly easy for me to describe herein the exact details of the fix. Having succeeding in this, my priority turns to my next project, rather than generating a minimal set of changes for a patch file... but if someone else wants to do that, to the end that it will be released into a new version of Win32::GUI, I'd be glad to share my changed files with them. If there is no hope of a new version of Win32::GUI, then after I'm done my next project, I might package and release all my changes in a branched version of Win32::GUI ... I guess it should be renamed, though, if it diverges from the original. ** I was debugging not only accelerator keys, but also resize cursor display (see recent message entitled "bug fix for Win32::GUI 0.0.665"), and attempts to debug the DoEvents double keystroke problem, although I gave up on that one for now. -- Glenn -- http://nevcal.com/ =========================== Like almost everyone, I receive a lot of spam every day, much of it offering to help me get out of debt or get rich quick. It's ridiculous. -- Bill Gates |
From: Erick B. <er...@je...> - 2003-11-07 16:52:28
|
On Wed, 05 Nov 2003 23:46:45 -0800, Glenn Linderman <pe...@ne...> said: > Hi, > > It was extremely important for my next project that I have accelerator > keys working in Win32::GUI (or whatever interface I chose to code to). > > As it turns out, there were only a few scattered places to fix things, > and I was able to get them working. However, along the way, for > debugging purposes (debugging several things, see ** below), I have > changed or rearranged a fair number of lines of code in a few of the > source files. Hence, it is not particularly easy for me to describe > herein the exact details of the fix. > > Having succeeding in this, my priority turns to my next project, rather > than generating a minimal set of changes for a patch file... but if > someone else wants to do that, to the end that it will be released into > a new version of Win32::GUI, I'd be glad to share my changed files with > them. If there is no hope of a new version of Win32::GUI, then after > I'm done my next project, I might package and release all my changes in > a branched version of Win32::GUI ... I guess it should be renamed, > though, if it diverges from the original. Glenn, Why don't you use CVS (the one already setup on SF.net) for all these much appreciated changes? It is indeed much easier to keep track of everything that way. -- Erick |
From: Glenn L. <pe...@ne...> - 2003-11-07 19:47:25
|
On approximately 11/7/2003 8:51 AM, came the following characters from the keyboard of Erick Bourgeois: > On Wed, 05 Nov 2003 23:46:45 -0800, Glenn Linderman <pe...@ne...> said: > > >>Hi, >> >>It was extremely important for my next project that I have accelerator >>keys working in Win32::GUI (or whatever interface I chose to code to). >> >>As it turns out, there were only a few scattered places to fix things, >>and I was able to get them working. However, along the way, for >>debugging purposes (debugging several things, see ** below), I have >>changed or rearranged a fair number of lines of code in a few of the >>source files. Hence, it is not particularly easy for me to describe >>herein the exact details of the fix. >> >>Having succeeding in this, my priority turns to my next project, rather >>than generating a minimal set of changes for a patch file... but if >>someone else wants to do that, to the end that it will be released into >>a new version of Win32::GUI, I'd be glad to share my changed files with >>them. If there is no hope of a new version of Win32::GUI, then after >>I'm done my next project, I might package and release all my changes in >>a branched version of Win32::GUI ... I guess it should be renamed, >>though, if it diverges from the original. > > > Glenn, > > Why don't you use CVS (the one already setup on SF.net) for all these > much appreciated changes? It is indeed much easier to keep track of > everything that way. Erick, That's a great suggestion. Except. 1) I don't have CVS installed; I haven't used it for about 6 years, and then only in an environment where there were explicit step by step instructions for that particular task (which isn't to say I don't understand source control facilities 2) I became an expert in ClearCase for a while, and PVCS/RCS, and SCCS in past lives, but just never have used CVS much) 3) I doubt that I have write permission enabled for the CVS repository; I'm going through the learning curve for Perl5 internals, Win32::GUI, and Windows's GUI API all at once, and I'm not sure I have the bandwidth for a CVS + Sourceforge learning curve too 4) There needs to be some coordination with Aldo, perhaps, and he hasn't responded publicly or privately to any of the email I've sent him regarding bugs over the last couple years. Or is the community ready to proceed without Aldo? 5) and because of the learning curves, I'm adding lots of debugging #if/#ifdef code all over Win32::GUI, and I'm not sure the real maintainers (if there are any left) would want all that cluttering the source code. So, if the changes are appreciated, and someone that is an expert in CVS + SourceForge wants to help me overcome the difficulties #1-3, and claim that #4 and #5 aren't problems, then I'd be glad to do just that. If not, well, maybe when I finish my current project (Feb or March?) then I'll look into tackling those learning curves without an expert. That said, I think it only took a dozen or so of real code changes to get accelerator keys working.... although I was really scratching my head trying to find one missing line... until I realized it was completely missing. -- Glenn -- http://nevcal.com/ =========================== Like almost everyone, I receive a lot of spam every day, much of it offering to help me get out of debt or get rich quick. It's ridiculous. -- Bill Gates |
From: Steve P. <st...@ba...> - 2003-11-15 18:58:57
|
Hi, I've recently been looking into the flickering resize in win32::gui. The most compatible solution to this I've found is extremely (and very annoyingly) simple. Just add the style WS_CLIPCHILDREN to your window or dialog box. I tried to implement double-buffering in GUI.xs (I was working with 0.0.558 at the time) but frankly I failed. Steve |
From: Steve P. <st...@ba...> - 2003-11-16 18:07:55
|
Hi, In my previous message I explained how to stop flickering in Win32::GUI. It turns out that this technique regularly causes widgets to leave imprints behind. Imprints dont seem to be left if widgets dont overlap, though. As I mentioned before I was already looking at painting off-screen, but I can't seem to get it to work. To solve this problem completely, Win32::GUI should do *all* painting in WM_PAINT. rather than painting individual widgets as they change size, and should ignore WM_ERASEBKGND messages. I tried to implement this, but I'm having trouble navigating the Win32::GUI source. If anyone wants to take on the flickering problem I'd be happy to help out with it. Steve ----- Original Message ----- From: "Steve Pick" <st...@ba...> To: "Win32 GUI" <per...@li...> Sent: Saturday, November 15, 2003 7:00 PM Subject: [perl-win32-gui-users] Solution: flicker in Win32::GUI > Hi, > > I've recently been looking into the flickering resize in win32::gui. The > most compatible solution to this I've found is extremely (and very > annoyingly) simple. Just add the style WS_CLIPCHILDREN to your window or > dialog box. > > I tried to implement double-buffering in GUI.xs (I was working with 0.0.558 > at the time) but frankly I failed. > > Steve > > > > ------------------------------------------------------- > This SF. Net email is sponsored by: GoToMyPC > GoToMyPC is the fast, easy and secure way to access your computer from > any Web browser or wireless device. Click here to Try it Free! > https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl > _______________________________________________ > Perl-Win32-GUI-Users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users > |