[Kommander-devel] Emergency call, please help...

[Eric Laffoon]

On Wednesday 09 February 2005 12:41 am, Andras Mantia wrote:
> On Wednesday 09 February 2005 08:43, Michal Rudolf wrote:
> > Right, problem with your dialog is similar, although the problem with
> > Wizard is known to be caused by internal (Q)Wizard handling in Editor
> > while Dialogs worked smoothly so far.
>
> The problem seems to be the reparent in widgetfactory.cpp:
>     if (parent && !parent->inherits("MainWindow"))
>       wiz->reparent(parent, QPoint(0, 0), TRUE);

I just took a look at this. The file is at 1.17 and this was changed in 1.16 
by Michal, however the line was copied out of the old code. I don't know if 
this is where behavior changed but I do know two things. For one, I think the 
inheritance issue is likely to come up with the base class because I believe 
Marc derived it in some way to be compatible with or from a widget class... 
so it may be we need to consider a supplemental class or some creative coding 
here. The other is what Michal told me about ugly hard coded widgets is 
really true. What a mess! Are we absolutely sure the plugins work? We really 
should make a plugin widget soon just to see how it functions and whether the 
concepts are functionally sound. It seems pretty untested with all we have 
done.
>
> As it some cases such a reparent is called for QDialog's as well (some
> lines above), might explain why it happens for some dialogs.
> This "hangup" is really challenging BTW, as the application gets locked
> in t he main event loop which is rather strange and might be cause by
> things like keyboard/mouse grabbing, altough I cannot find anything
> like that here.
>  And Designer does the same, so ... I don't know what can be the
> problem.
>
> Andras
The behavior is consistent historically. There have always been some degree of 
problems with trying to work with anything but dialogs. I'll test some 
mainwindow files and see what they do.
-- 
Eric Laffoon
Project Lead - kdewebdev module