thanks a lot for these informations.

3) When loading TWM + Keymapping, I realized the cmd+w was not working again.�� Wandering, I found that the TWM shortcuts were defined for a lot of morphs, in this way, causing a little of trouble:

�� {PasteUpMorph. SystemWindow. SmalltalkEditor. TextEditor. PluggableTextMorph} do: [:aClass|
�� aBuilder
�� attachShortcutCategory: self shortcutCategory
�� to: aClass.
�� ].

But replacing it by

aBuilder
�� attachShortcutCategory: self shortcutCategory
�� to: PasteUpMorph.

should be working the same way :/.
Laurent, did you have any problems when not attaching the categories in this way?.

I think I've done that because TWM shortcuts are not handled when the focus is on a TextEditor, because of the cmd+w collision.��

��

Also: TWM by default has a lot of (cmd+w, ...) mappings colliding with the window cmd+w shortcut.�� So the window shortcut or the TWM ones are to be sacrificed :P.

OK so cmd+w is definitely not a good prefix for TWM shortcuts. Is cmd+m ��better ?��

��

So i installed TWM without keybinding but now I cannot open the settings window because keymappings is not load.

Any solution? (install TWM without keymappings or fixing keymappings)

I've done some fixes and improvements to keymapping, and I've created a 2.0 version where:

- the collisions below are fixed
- keymaps can be configured per morph instance too (not only per class, as the former version)
- some little improvements and code cleaning

Thanks !

��

But those things I remarked of TWM should be reviewed :)

Or you can Use twm without keymappings and I'll have no more feedback :(

TWM without Keymapping is not really interesting. I will produce new versions of TWM.

Laurent

��

��

thanks!

Thank you :)

Guille