11:07:45scymtymbut i don't see the problem. i invoked FOO from the menu. that causes an accepting values "mini dialog" to be displayed in the interactor
11:08:10scymtymthe dialog has two arguments and i can switch between them and edit freely before submitting the command
11:08:30scymtym(i think the command output goes to the other pane and is erased during redisplay)
11:08:59lokewhat if you type "Foo" in the interactor and press return?
11:10:19scymtymi see. in that case, i can edit the arguments once but trying to switch back to the first arguments makes both immutable
11:11:11scymtymso the problem involves the commandline parser /and/ accepting values
12:43:52jackdanielscymtym: do you think that top-level-sheet-mixin should have default initargs for the name, the pretty name and the icon? i.e 'top-level "(unnamed sheet)" and nil
12:45:11scymtymjackdaniel: i will have a look in a bit
13:01:08scymtymjackdaniel: it seems that, depending on the use of the mixin, different defaults (or lack of those) are appropriate. so i would put those defaults into a STANDALONE-TOPLEVEL-SHEET class or similar, assuming that is the use case
13:06:45jackdanielwhat would be the purpose of lack of defaults? slots are unbound them
13:10:59jackdanieldefaulting to (alexandria:required-arg :foo) would be better, if we don't want to provide default values
14:02:12scymtymi meant defaults that are definitely immediately replaced, as is the case when the sheet is the t-l-s of a frame, wouldn't make sense and could be confusing