On Tuesday 04 May 2004 8:07 pm, Andre Poenitz wrote: > On Tue, May 04, 2004 at 04:15:49PM +0100, Angus Leeming wrote: > > Maybe we should do as John has done in the Qt frontend already > > and have separate widgets to display messages and to input > > commands? > > Btw, I discovered today that there's a Qt "WidgetStack" (or > similar) Why don't we use this for minibuffer + status bar?
Good question. From the docs: The QWidgetStack class provides a stack of widgets of which only the top widget is user-visible. The application programmer can move any widget to the top of the stack at any time using raiseWidget(), and add or remove widgets using addWidget() and removeWidget(). It is not sufficient to pass the widget stack as parent to a widget which should be inserted into the widgetstack. My take on this: QWidgetStack is the way to go if we want to emulate emacs' minibuffer. Ie, a single 'apparent' widget that both displays messages and receives input. However, John has argued that these requirements are best served by two, separate widgets. I tend to agree with him. Have you tried the Qt frontend, Andre? Fire it up and the 'status bar' is visible but the 'minibuffer' is not. Type M-x and the 'minibuffer' appears, allowing you to input data. Personally, I'd prefer it if this minibuffer subsequently disappeared again. Indeed, John was talking about an lfun to hide these toolbars. Dunno what happened to that. John? Angus
