From: <dan...@gm...> - 2005-07-20 16:55:44
|
Well, Please check: http://www.perlmonks.org/?node_id=3D476373 to see my problem :) Thanks, Daniel |
From: Robert M. <rm...@po...> - 2005-07-20 18:14:44
|
Daniel, Could you post a minimal example that exhibits this problem so that I=20 can verify and track it down. I have played with with the=20 TrackPopupMenu implementation in this release, but my testing didn't=20 show any such problems. Also what Perl version, and what windows platform? Regards, Rob. Daniel =C5kesson wrote: >Well, > >Please check: >http://www.perlmonks.org/?node_id=3D476373 to see my problem :) > >Thanks, >Daniel > > >------------------------------------------------------- >SF.Net email is sponsored by: Discover Easy Linux Migration Strategies >from IBM. Find simple to follow Roadmaps, straightforward articles, >informative Webcasts and more! Get everything you need to get up to >speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=CCk >_______________________________________________ >Perl-Win32-GUI-Users mailing list >Per...@li... >https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users > > =20 > |
From: Robert M. <rm...@po...> - 2005-07-20 19:58:23
|
Daniel =C5kesson wrote: >my($x, $y) =3D Win32::GUI::GetCursorPos(); > >$mw_win32->TrackPopupMenu($systray_menu->{SystrayMenu}, $x, $y); > =20 > > My most humble apologies. I've broken TrackPopupMenu() in a piece of=20 logic that I spent so long looking at that I was *sure* I had it=20 right. The fix is trivial, and I've put it into CVS. If you want to=20 build your own immediately I can send you a patch. If not try one of=20 these: $mw_win32->TrackPopupMenu($systray_menu->{SystrayMenu}); will, as of V1.02, do the GetCursorPos() for you. If you need backwards compatibility with earlier versions of Win32::GUI, = then $mw_win32->TrackPopupMenu($systray_menu->{SystrayMenu}, $x, $y, TPM_LEFTA= LIGN | TPM_TOPALIGN | TPM_LEFTBUTTON ); should work in all cases. (I've broken the 3-parameter call variant) I've raised a tracker: 1241830, so that there is visibility of the proble= m. Does anyone think this is serious enough (as it breaks backwards comp= atibility) to warrant thinking about another release? Regards, Rob. |
From: Robert M. <rm...@po...> - 2005-07-21 21:12:36
|
Glenn Linderman wrote: > On approximately 7/20/2005 12:58 PM, came the following characters > from the keyboard of Robert May: > >> I've raised a tracker: 1241830, so that there is visibility of the >> problem. Does anyone think this is serious enough (as it breaks >> backwards compatibility) to warrant thinking about another release? > > Well, it certainly warrants thinking about one :) And you've already > started thinking about one, or you wouldn't have written this! Indeed > It has bitten Daniel, and may bite others. If we are planning another > release in the near term (a month or so) I wouldn't think it is > necessary to put one out now. But if we are not planning another > release in the near term, then I would recommend doing one now to > avoid problems for other people. I would have though that targeting a bug-fix only release for a month's time might be realistic. I'd like to get the following done: - fix as many of the trackers as possible - get all the current sample code to work properly - include all the examples from the tutorial (and check that they all work :-), fixing the tutorial as necessary - work on the test suite - get a semi-decent web-page up as our Homepage at SourceForge. > If you do choose to make a new release, I am available to help with > the builds for the next week, after that it gets uncertain for a while. Thanks for you offer, but I now have an all-dancing MSVC++6 environment, so am reasonably self-sufficient in this regard. Regards, Rob. |