Hi nicolai
I can tell that I'm sad about the state of this part of the system.
I do not know how I can help fixing this. What is really important is
that we protect future brick from this mess.
I think that we should have a structure so that people writing code can
follow this structure.
I worked a lot trying to clean HandMorph (and my code was obsolete
because I was too slow to finish it and SDL arrived :)
May be one way would be to remove all the old hardcoded bindings.
Stef
Le 7/8/16 à 21:15, Nicolai Hess a écrit :
Oh well ....
Please take a look at the current implementation of event handling,
just 10 minutes or so.
how we use different (shortcut) event registration
shortcut handling
event handling
some are defined in code, some shortcuts handled by the editor , some
by the morph
some shortcuts are defined on the morph that gets the events, some are
defined on other morphs.
some event (shortcuts spotters dive in / dive out) only works
*because* we have the two shortcut handlers (handleKeystroke: /
dispatchKeystroke:)
and tell me that it is a good idea to just start introducing something new
I really think we should clean up what we have now or at least finish
the move to the kmdispatcher event handling.
