>>>>> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> On Wed, Jul 17, 2002 at 07:01:19AM +0200, Andre Poenitz wrote: >> ... but this sounds like a worthy goal. So I would not mind >> removing the message, but wait for other opinions. John> Sure. I'm finding various bits of the minibuffer state display John> rather confusing and awkward actually. Some random things : John> o why is commandshortcut a member of lyxfunc rather than an auto John> ? Don't know. John> o the string return from ::dispatch seems only used to get the ' John> ' added. This should be handled by the frontend instead I think One solution I had in mind is to have two virtual areas in minibuffer the left one for messages and the right one for shortcuts. The frontend would be responsible for deciding how to display that. The advantage is that it would suppress the need for addSet, which is really broken when used several times in a row. John> o miniDispatch can be cleaned away I think probably John> o addSet should be show_cmd_dispatched() or something more John> readable and it should be a frontend decision on whether to add John> it to the current thing or not or whatever See above John> o we show "at rest" something like "LyX: newfile.lyx (changed)" John> which duplicates the titlebar. I'd much prefer the "at rest" John> display to be the font mode status etc, especially as this will John> simplify implementation Yes, this would be much better. A plan I had some time ago is to make that configurable, so that people could show current font, file name, insets/environment nesting, whatever, with a simple string like "LyX: $$FName $$Changed" or "$$FontState" But this probably does not go in the direction of simplification you have in mind... I suspect that some people will be pissed offf to have the file name disappear in minibuffer, becasue they are not used to looking at titlebar. JMarc
