Colin. Hmmm.
So I put a "mouseEnter" handler in the stack script, and this does report whatever control the mouse runs over as it travels. I would have thought so myself. I cannot believe that I cannot call it at will from a running handler, though. This seems like a bug. Why so different from any other function? Craig Newman In a message dated 3/18/09 2:35:57 PM, co...@rcn.com writes: > You're still in the mouseup handler of the original control, and so I > guess that's the control that the handler still sees. > ************** Great Deals on Dell 15" Laptops - Starting at $479 (http://pr.atwola.com/promoclk/100126575x1220433363x1201394532/aol?redir=http:%2F%2Fad.doub leclick.net%2Fclk%3B212935224%3B34245239%3Bb) _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
