Changeset 19853

Timestamp:

03/03/07 23:07:15 (2 years ago)

Author:

patrick

Message:

Handle the case when the mouse pointer is within the bounds of a view
when the window containing the view is first opened. The reason this case
requires special handling is because the response to the mouseEntered
event is needed to get proper notification of mouse movements within the
view. As far as I can tell, there is no other way to get a mouseEntered
event without having the user move the mouse outside the window and then
back inside.

This takes care of the last of the known bugs with the Cocoa input windows.

Files:

• juggler/trunk/modules/gadgeteer/gadget/Devices/KeyboardMouseDevice/InputViewCocoa.mm (modified) (2 diffs)

juggler/trunk/modules/gadgeteer/gadget/Devices/KeyboardMouseDevice/InputViewCocoa.mm

@@ -27 +27 @@
-#include <gadget/gadgetConfig.h>
-
+#import <Foundation/NSString.h>
-#import <AppKit/NSWindow.h>
-#import <AppKit/NSEvent.h>
@@ -108 +109 @@
-      [super viewDidMoveToWindow];
-      [self resetTrackingRect];
+
+      // If this view was moved to a new window, determine if the mouse is
+      // currently within the bounds of this view. If it is, then we post a
+      // fake mouseEntered event to inform this view that the mouse is within
+      // it. Without this, the user would have to move the mouse out of the
+      // window and back in to get the mouseEntered event to be posted.
+      if ( [self window] )
+      {
+         const NSPoint mouse_loc =
+            [[self window] mouseLocationOutsideOfEventStream];
+         const NSRect bounds = [self bounds];
+
+         if ( [self mouse:mouse_loc inRect:bounds] )
+         {
+            // XXX: Would it work better to use CGPostMouseEvent() here?
+            [self mouseEntered:nil];
+         }
+      }
-   }
-