Nice investigation. This should go in the docs somewhere, particularly that
parents gadget must pass gestures to the parent for the actions to work.
For example in
http://docs.factorcode.org/content/article-action-gestures.html ?
diff --git a/basis/ui/gestures/gestures-docs.factor
b/basis/ui/gestures/gestures-docs.factor
index a12ec35..f7e034f 100644
--- a/basis/ui/gestures/gestures-docs.factor
+++ b/basis/ui/gestures/gestures-docs.factor
@@ -430 +430 @@ ARTICLE: action-gestures Action gestures
-The following keyboard gestures, if not handled directly, send action
gestures:
+The following keyboard gestures, if not handled directly by any gadget in
the hierarchy until reaching the world, are re-sent as action gestures to
the first gadget:
Also, in worlds.factor:
action-gestures [
[ [ { C+ } ] dip f key-down ]
[ '[ _ send-action ] ]
bi*
] H{ } assoc-map-as
so macos has the some actions with the command keys from
./basis/ui/backend/cocoa/views/views.factor and also the actions from the
control key resent by the world ? Maybe add a note for that describing the
exact mechanism.. I haven't read the code and don't have a mac to confirm
how it works, but is it something like Additionally, On Mac OS X, action
gestures are directly sent when using the Command key or Menu Items ?
Jon
On Mon, Aug 24, 2015 at 12:08 PM, Georg Simon georg.si...@auge.de wrote:
As far as I understand the answer to my question is as follows :
editor passes C+c, C+s, and so on to it's parent. All parents should
pass them too. In world waits a gesture-handler. It handles keypresses
for which action gestures exist. The corresponding action gesture is
sent to editor. editor either handles the action gesture or passes it to
it's parent.
http://paste.factorcode.org/paste?id=3608
--
___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
--
___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
