Filip Šikula

I am also having this problem, any updates on this?

I can confirm this problem. When guard method prevents execution, Caliburn disables the control associated with the action. In this case it disables whatever control has the [KeyTrigger](https://github.com/Caliburn-Micro/Caliburn.Micro/blob/f435e3c21ec20a56b905ff50a8a1eae3c1b7789c/samples/scenarios/Scenario.KeyBinding/Input/KeyTrigger.cs), since it...

Possible solution might be addition of new dependency property to [ActionMessage](https://github.com/Caliburn-Micro/Caliburn.Micro/blob/63a49070f765c126d73171722b30f4ca7471ab6d/src/Caliburn.Micro.Platform/ActionMessage.cs) that would prevent it from applying availability effects to the associated Control. This might also come in handy outside...

Yes, omitting the `CanExecute` method is the simplest answer. But the problem, in my opinion, is in the usability. Imagine a scenario where you have some buttons, all of them...

Thank you for a quick response and subsequent pull request. I have one more thing, regarding item container customization. When the control is in edit mode, the selected item has...

I am also having this issue with v0.0.6535.20611-pre and v0.0.6330.3877-pre.

Thank you for the fix. I have also encountered this problem recently and this resolves the issue.

Thanks for doing this. But this PR does not close the issue. It only solves the problem when using the ActionMessage directly, not what the issue initially described. Since you...

I also think, that this change should not be structured as a way to "ignore guard" property. Right now, when you use the keyboard shortcut, and the guard property is...

@KasperSK Maybe naming it `ResolveAvailability` or `SkipAvailabilityResolution` would be better? Since you are not skipping an update but preventing availability from been resolved in the first place? I think that...