modules/rkt: first stab at scene editing for scener

This augments the NEWSCENE_SETUP state to also handle editing
existing settings, which is slightly different but actually
overlaps with the already implemented invalid input stuff.

There's still work to do, and the UX is kind of awkward at best.

But this takes us from having no ability to edit existing scenes,
to being able to actually make edits interactively while it's all
live... with a modicum of interactive guidance via the setup
machinery.

It basically behaves just like creating a new scene, except
instead of the <enter>-accepted "preferred" values, you accept
the existing relevant setting.  So as-is, when editing, you have
no shortcut for getting back the "preferred" value for a given
setting.  That's been replaced with the existing value for that
setting.

You also get seemingly spurious redundant queries for module
names in things like compose::layers, but they're really not the
same since the first time you get asked it's actually the full
settings string you're getting an opportunity to specify
wholesale, but can accept to seed the layer's settings as-is,
which you will then be given an opportunity to edit piecemeal.
It's that subsequent piecemeal editing of the individual settings
within the nested instance that can feel like a spurious
duplication, especialy when a given layer has just a bare-value
module name and no subsequent settings.. like "plasma".  You'd be
asked if you want "plasma" for the layers/[N], then asked if you
want "plasma" _again_ for the layers/[N]/[0] since the module
name is an unnamed setting at position 0 within the layers/[N]
instance.

It was tempting to try streamline that a bit, but there's
actually utility in having an opportunity to paste in a full
settings string for the layers/[N] if you have a serialized scene
onhand you want to dump in there.  Then after that, you can juts
smash enter as much as necessary to accept what you pasted in
without editing those in the piecemeal phase.  Or, if there was
actually something in what you pasted you did want to change,
change it during that piecemeal phase.

I think it at least kind of works.

0 files changed, 0 insertions, 0 deletions