Best way to manage state?

[MayRedwood]

The documentation didn't really make this clear - what's the recommended way to manage state in Ignis? Variables, Services, something else?

For context on my specific usecase: I want my media widget to keep track of the "currently selected" player (something akin to playerctld), with functions to change the selection. For that, I'll need to keep track the name/id/something else of the current player. How would I go about doing this?

[linkfrg]

If you need the notify signal to emit when the value changes, go with Variable. Otherwise, you can store it either as a global variable or as a class attribute (if you use classes).

[MayRedwood]

Thank you! This is unrelated, but I'd rather not open a different discussion - how would I run an arbitrary function from my config.py from the CLI? In my case, functions for play-pausing a media player, changing the currently selected player, etc.

[linkfrg]

There is no convenient way to do it (see #315), but you can write some script and run it using ignis run-file. It will be launched inside the Ignis process, giving access to all services, e.g., you can do MprisService.get_default() as usual. But I am unsure is it possible to import something from config.py

[MayRedwood]

I figured out how to import from config.py, but it is noticeably slow (I assume because of the python cli's startup time). Will #315 have goignis support?

[lost-melody]

Will #315 have goignis support?

Yes, goignis will support Command then.

Currently, a work around is to create a DBusService that provides Play/Pause methods, and call them by dbus-send.