Open choppeh opened 4 months ago
This is not supported by flatpak override
. If we find some hacks to implement it inside the flatpak overrides, this is not guarantee to continue to work. And implementing outside of flatpak overrides is much work for little use IMHO.
What you are more interested in is flatpaks command-line, e.g. flatpak run --env=QT_QPA_PLATFORM=wayland --filesystem=~/Downloads/test --unshare=wayland --share=x11 com.example.App
.
This is not supported by
flatpak override
. If we find some hacks to implement it inside the flatpak overrides, this is not guarantee to continue to work. And implementing outside of flatpak overrides is much work for little use IMHO. ...
It's not a flatpak feature, but a UI feature
Something like applying the settings if it's enabled.
Instead of just allowing deletion, also disable (without losing the settings added)
Like this
Or
Disable custom properties without removal
So you are fine with in-memory only state? I.e. when you close/restart flatseal the UI is reset to the state (enabled or deleted, not disabled) when you closed flatseal?
So you are fine with in-memory only state? I.e. when you close/restart flatseal the UI is reset to the state ...
Sorry, disregard the ‘temporary’ in the previous messages, it's just a feature to disable and enable settings in the UI, but in the sections where the user can enter configuration.
But I don't mind if it's just in-memory
I sometimes configure environment variables to test certain application options, and I find it interesting to be able to quickly enable or disable these settings without having to delete a previously defined environment variable.
For example. I set the variable.
But to disable this setting, I end up removing this option, but I just wanted to test without it temporarily.