We digged a bit more, and we think it's definitely a bug in Keymapping.

The problem is made obvious by the global shortcuts recently introduced:
https://github.com/pharo-project/pharo-core/commit/d7ff3a9a65273292a764fc8e8012df07169acb4d

Some shortcuts start with Cmd+o and add something else (for example, Cmd+o, Cmd+s opens the settings browser).

The problem is that if you only press Cmd+o, the event is swallowed and the Cmd+o defined locally no longer triggers.

If you disable all global keybindings that start with Cmd+o:
((self globalCategories flatCollect: [ :each | each allEntries keymaps ])
select: [ :each | each shortcut beginsWith: $o command ]) do: #disable

you can again use the shortcuts locally:
((PluggableTextMorph
on: 'haba'
text: #asText
accept: nil)
bindKeyCombination: $o command toAction: [ 'does not halt' halt ];
bindKeyCombination: $/ command toAction: [ 'it halts' halt ])�
openInWorld

Doru



On Thu, Mar 20, 2014 at 6:54 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,

We (Andrei and I) are experiencing some strange behavior recently related to keybindings.

In the example below:
- pressing "Cmd+/" brings up the halt
- pressing "Cmd+o" does not bring up the halt

((PluggableTextMorph
on: 'haba'
text: #asText
accept: nil)
bindKeyCombination: $o command toAction: [ 'does not halt' halt ];
bindKeyCombination: $/ command toAction: [ 'it halts' halt ])�
openInWorld

One difference between the two is that Cmd+o is already define inside the text morph, while Cmd+/ is not. However, this used to work in�30796 but does not work in�30798.

I do not have time right now to look at it more deeply. Do you know why the behavior changed suddenly? What should we adapt?

Doru

--

"Every thing has its own flow"



--
www.tudorgirba.com

"Every thing has its own flow"