on 1/15/06 12:28 PM, John McKernon at [EMAIL PROTECTED] wrote: > I tried Phil's "new event" suggestion, which is pretty cool (and I learned > something from it), but has a fatal flaw: The MouseUp event doesn't fire > unless you pass True to the MouseDown event, and when you do that RB assumes > you're handling the whole shebang and nothing pops up at all.
Since reading this, I tried it as well... and it does seem to be fatally flawed. It seems that if you return True from the PopupMenu.MouseDown event, the PopupMenu does not expand. Since it is necessary for the PopupMenu.MouseDown to return True in order to enable the MouseUp event, and the MouseUp event is supposed to return the x-y coordinates where the Mouse Button was released within the Control, this tells me that there is an RB BUG responsible; after all, how would one go about returning the x-y coordinates where the mouseButton is released of you cannot get the mouse to a point where that information is meaningful? Either one or two things are wrong... maybe both: Either the MouseDown event should NOT be preventing the PopupMenu from expanding; OR... There should be a method which can be invoked to expand the PopupMenu upon command. The only possible workaround I can think of is that perhaps there is a Declare that can be accessed via the PopupMenu's handle, that can be used to prod the thing open in the MouseDown event. I haven't got time to look ito that myself, right now. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
