Well, currently the only implication is that I don't get a wait cursor
when I hit the Enter key on my dialog if the mouse hasn't moved. So,
not a real big deal.
~Roger
On 6/14/11 5:52 PM, Greg Brown wrote:
Actually, it is supposed to work as you describe.
TerraDialogSkin#windowOpened() calls reenterMouse() on the display,
which should trigger a mouse over on the current component. However,
after stepping through the code, I see a number of reasons why this
does not happen. I'm not sure yet what the right solution might be.
How big of an issue is this for you?
G
On Jun 14, 2011, at 6:53 PM, Roger L. Whitcomb wrote:
Question: if I have a button (for instance) which when pressed opens
a dialog such that this dialog is positioned right where the button
is, so that it obscures the button, should there be any component on
the new dialog that has “isMouseOver()” true (without moving the
mouse after the dialog opens)? It seems like there isn’t any until
the mouse moves, although I haven’t conclusively proven that. But,
should the dialog/window “open” trigger a pseudo-mouse move so that
the component now under the mouse has its “mouseLocation” set? Or am
I asking too much?? Thanks.
*Roger Whitcomb*
Architect, Engineering
*Ingres Corporation***
[email protected] <mailto:[email protected]>
*PHONE*+1 650.587.5596
*FAX*+1 650.587.5550
*www.ingres.com* <http://www.ingres.com/>
This transmission is confidential and intended solely for the use of
the recipient named above. It may contain confidential, proprietary,
or legally privileged information. If you are not the intended
recipient, you are hereby notified that any unauthorized review, use,
disclosure or distribution is strictly prohibited. If you have
received this transmission in error, please contact the sender by
reply e-mail and delete the original transmission and all copies from
your system.
