2010/5/18 Fernando olivero <[email protected]> > The DNU is reported in ISSUE 1876. >
Yes, it was complicated to use Man Menu in Pharo 1.1 Alain was working on that....but as he doesn't have a mac... I needed to enable Mac Menu because I was trying to remove it from core and put it in dev or in PharoNonCore, but if it even doesn't work it does not have sense. Cheers Mariano > > Begin forwarded message: > > *From: *Fernando olivero <[email protected]> > *Date: *May 18, 2010 4:22:43 PM GMT+02:00 > *To: *"[email protected] Development" < > [email protected]> > *Subject: **[Pharo-project] Pharo1.1 and Pharo1.0 difference when pressing > CMD-Q* > *Reply-To: *"[email protected]" < > [email protected]> > > Hi, using the MAC OS X VM and pressing CMD-Q in Pharo1.1 sends > InputEventSensor>>processEvent: evt > where the evt received is of type 4, a menu event. (just put a Transcript > show: evt in the processEvent: evt and you'll see). > > Since EventSensorConstants defines: > > "Types of events" > EventTypeKeyboard := 2. > EventTypeMenu := 4. > > But in Pharo1.0 it generates an event of type 2, a keyboard event. > > I assume that this changed because In Mac-OSX the CMD-Q is binded to a > particular action , > and in Pharo1.1 we are using HostSystemMenus. > > But how can i override this behavior? To handle the CMD-Q as any other > Keyboard event? > > By the way there's also a DNU, when pressing CMD-Q. > > Thanks, > Fernando > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
