Hi,

I think it is a good time for a new release - lot of bug fixes and minor
enhancements since the last release.

> I was working on trying to transform the WM_NOTIFYICON code from the
> standard message loop to work in the NEM message loop, and allow
> AddNotifyIcon to take -onClick -onRightClick and -events parameters,
> with the -events allowing Click and RightClick.  Then I noticed
> MousEvent in the default case, I guess we'd need -onMouseEvent for that?

Some other controls suffer from a similar situation. For example the tree
control is missing NEM rightclick and other mouse releated events.

> I haven't really figured out the "correct" data structures for where to
> put the sub refs for -onClick etc. so that they can be found and called
> via DoEvent_NEM... that was what I'd hoped to figure out tomorrow or so.
> Or else to invent a new DoEvent_NEM type function that accepts the sub
> ref as a parameter, and does all the standard Perl interfacing.
> Depending on what I could figure out.  I'd rather not hold anything up,
> but I need NotifyIcon support if I'm going to use NEM.

I had a quick look at the source that Laurent has been working on - it's
much cleaner. One question though - where will code go that handle the
events? It would be nice if there is a relative simple and straightforward
process to add additional events to controls without having to jump through
lots of hoops. There have been several times I have considered adding new
events to controls, only to be confused in the process:)

Cheers,

jez.


Reply via email to