From: Robert M. <rob...@us...> - 2007-07-26 20:03:17
|
On 25/07/07, Salvador Ortiz Garc=EDa <so...@ms...> wrote: > On Wed, 2007-07-25 at 16:29 +0300, Veli-Pekka T=E4til=E4 wrote: > > Hi list, > > I think I've found a bug or oddity in Win32::GUI::AcceleratorTable > > ... > > Yes, right now only the internal handlers are stored in the associated > window, a bug IMHO. Probably, but it's not a straightforward fix. > BTW the same happens with a menu. and fonts, and probably other non-window objects. > As time permits I've be working in a proper fix, That's great - I look forward to it. You might want to have a discussion with me about this, as I've looked into it briefly before, and if I remember correctly there are a number of edge cases to watch out for. > but as a quick > workaround in my apps I store the perl objects in the window hash: It's better practice to use the UserData() or ClassData() methods to store data with a window - that's the documented interface - and will remain supported. Poking directly into the representation of an Object is unhealthy. Regards, Rob. |