| Trolltech Home | Qt-jambi-interest Home | Recent Threads | All Threads | Author | Date | |
| All threads index page 1 | |
Hi! I've tried to update Moonlight|3D from the last Qt Jambi RC to the final release and apart from some function renaming in Qt that was easily fixed I have one problem left that I do not fully understand: In one case (I can't yet specify the exact reasons, unfortunately) the layouters seem to ignore the spacing between widgets that I explicitely set to 0 and add visible spacing between widgets. This spacing goes away, when one of the child widgets gets resized. It might be that I'm stumbling over some strange corner cases because I use a lot of nested widgets with forced minimum and maximum sizes. I definitely need to experiment some more myself to be sure. But this still leaves a question: was there an intended change in the layouter behaviors between the last release and this? Regards, Gregor -- [ signature omitted ]
Attachment:
signature.asc
Description: This is a digitally signed message part.
Gregor Mückl wrote: > Hi! > > I've tried to update Moonlight|3D from the last Qt Jambi RC to the final > release and apart from some function renaming in Qt that was easily fixed I > have one problem left that I do not fully understand: > > In one case (I can't yet specify the exact reasons, unfortunately) the > layouters seem to ignore the spacing between widgets that I explicitely set > to 0 and add visible spacing between widgets. This spacing goes away, when > one of the child widgets gets resized. It might be that I'm stumbling over > some strange corner cases because I use a lot of nested widgets with forced > minimum and maximum sizes. I definitely need to experiment some more myself > to be sure. > > But this still leaves a question: was there an intended change in the layouter > behaviors between the last release and this? I can't reproduce this myself. Do you have some sourcecode I could look at to investigate further? - Gunnar
On Friday 15 June 2007, Gunnar Sletta wrote: > Gregor Mückl wrote: > > Hi! > > > > I've tried to update Moonlight|3D from the last Qt Jambi RC to the final > > release and apart from some function renaming in Qt that was easily fixed > > I have one problem left that I do not fully understand: > > > > In one case (I can't yet specify the exact reasons, unfortunately) the > > layouters seem to ignore the spacing between widgets that I explicitely > > set to 0 and add visible spacing between widgets. This spacing goes away, > > when one of the child widgets gets resized. It might be that I'm > > stumbling over some strange corner cases because I use a lot of nested > > widgets with forced minimum and maximum sizes. I definitely need to > > experiment some more myself to be sure. > > > > But this still leaves a question: was there an intended change in the > > layouter behaviors between the last release and this? > > I can't reproduce this myself. Do you have some sourcecode I could look > at to investigate further? > > - > Gunnar Hi! In my attempts to get to the bottom of this I've found a workaround that works for me now. This issue seems to be related somehow to widgets that get added to child widgets which are managed by a layouter. It seems to me that the layouter then adds spacing before this widget, which goes away when its size constraints are updated. I am well aware that this description is still very vague and probably not enough to generate test case from. I know I should probably provide you with one of my own, but I fear that the complexity and quirkiness of my code won't help you much in debugging this. Regards, Gregor -- [ signature omitted ]
Attachment:
signature.asc
Description: This is a digitally signed message part.
Gregor Mückl wrote: > > Hi! > > In my attempts to get to the bottom of this I've found a workaround that works > for me now. This issue seems to be related somehow to widgets that get added > to child widgets which are managed by a layouter. It seems to me that the > layouter then adds spacing before this widget, which goes away when its size > constraints are updated. Is this bug visible anywhere in the moonlight packages?