From Clotilde
This interaction manages ALL keyboard interactions with the canvas. It is by default in RSCanvasController.
Problem: we want to add a shortcut to a presenter that includes a SpRoassalPresenter, containing a RSCanvas, thus using this interaction. Our shortcut needs to strike $M and this keystroke is preempted by the canvas to expand the window.
We can either
Remove the interaction from our RSCanvasController, but then we lose other keystrokes (i, o, arrows)
or we have to implement a subclass of RSKeyNavigationCanvasInteraction with an empty #processKeyUp:; and a subclass of RSCanvasController using our subclass. Not very elegant.
Maybe this interaction should be split in several ones to manage different kinds of effect. Or maybe should we be able to set the key to strike for each action?
Version information: Moose 11 image (Roassal v1.05b)
From Clotilde This interaction manages ALL keyboard interactions with the canvas. It is by default in RSCanvasController. Problem: we want to add a shortcut to a presenter that includes a SpRoassalPresenter, containing a RSCanvas, thus using this interaction. Our shortcut needs to strike $M and this keystroke is preempted by the canvas to expand the window.
We can either
RSCanvasController, but then we lose other keystrokes (i, o, arrows)RSKeyNavigationCanvasInteractionwith an empty#processKeyUp:; and a subclass of RSCanvasController using our subclass. Not very elegant.Maybe this interaction should be split in several ones to manage different kinds of effect. Or maybe should we be able to set the key to strike for each action?
Version information: Moose 11 image (Roassal v1.05b)