Its a common practice in such cases (like in newRectFrom:) to capture a mouse events directly. So, i'd rather add a method to Hand or less likely Sensor, which will hide details from consumer and could be used like: Word activeHand captureMouseDuring: [:event | .. process the event ... event anyButtonPressed "if block returns true - keep capture and release otherwise , on non-local return - release as well" ] 2009/2/15 Igor Stasenko <siguctua@gmail.com>:
2009/2/15 Hilaire Fernandes <hilaire@ofset.org>:
I suspect external applicatiom may want this method
As to me, this is too low-level for external app to bother with. See how much handing it needed to work correctly in #newRectFrom:. There is also an equivalent ways to synthesize events using morphic.
2009/2/15 Igor Stasenko <siguctua@gmail.com>:
Hi, i found this method used only in two places in my image:
Rectangle>>newRectFrom: Rectangle>>newRectButtonPressedDo:
i think it could be candidate for removal along with #newRect's
Still, i think it is useful to create graphics primitives based on user input. But i think that Rectangle is inappropriate place for it, where it hard-wiring with many globals and Morpic framework.
-- Best regards, Igor Stasenko AKA sig.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- http://blog.ofset.org/hilaire
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.