gigafalk at yahoo.com
Tue Jun 27 21:36:34 UTC 2000
John Birch wrote:
> In the case of the debugger there is one controlling widget, lets call it
> dbgManager (surprise :-)
To my mind dbgManager shouldn't be a widget but a class that has got widgets
and it can access those widgets.
I suggest to let this manager emit the signals:
> The problem is that this widget has multiple sub widgets that want to be
> docked. So my question stands. How does a part make these subwidgets without
> knowing about docking?
You access the widgets directly via dbgManager (that is no widget) and do what
you have to do there (e.g. fill with data, draw funny bubbles or ...)
Why do you want to know about docking?
> Is the widgetCreated signal an option? And arn't the position hints
> dockwidget specific so that the part cannot know this?
Abstract information (abstract type descriptors) and placing hints or QString
descriptors should be transfered to give the main GUI control a chance to know
a little bit more than just QWidget* xyz.
F at lk
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
More information about the KDevelop-devel