A case for keeping App.bind() (or extend the scope of dynamic actions)?

[grota]

I am currently using App.bind() to define dynamic bindings, but dynamic for the keys not in the dynamic action + check_action sense.
In other words I'm providing a keybinding settings feature where users can choose what keys to use (for some actions).
Unless I'm missing something obvious using the BINDINGS class var is a no go for me since I'm using a context var for the settings which is set at runtime and not at import time.

SETTINGS: ContextVar[Settings] = ContextVar("settings")

(I copied the approach from posting)

using App.bind() is the only (clean) way for me now to define "dynamic" (as in customizable) bindings at runtime, so I'm advocating for either keeping it or expand the scope of dynamic actions to support this use case 😄

Thoughts?

[TomJGooding]

Have you looked at set_keymap? I'm pretty sure that's how Posting achieves this.

[grota]

Thanks, looks promising! I'll look into it and let you know!

[grota]

Looks like it fits perfectly for my use case, thank you again!