Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

Layout, widgets not inside ???



  • I have an XML file where I have added a group box, the group box has an attribute layout:

    <groupbox id="enSEX" eol="true" align="left" layout="vertical" 
    	  dbfield="vcSex">
        <radiobutton id="rdoM" text="Male" default="true" position="0,0"/>
        <radiobutton id="rdoF" text="Female" position="1,0"/>
    </groupbox>
    

    In my common node code:

        if ( mstrName.compare(clsCNT::mscszGroupBox) == 0 ) {
    //Any layout specified?
            QString strLayout(strGetAttribute(clsXMLnode::mscszAttrLayout));
            if ( strLayout.compare(clsXMLnode::mscszLayoutGrid) == 0 ) {
                mpobjLayout = new QGridLayout;
            } else if ( strLayout.compare(clsXMLnode::mscszLayoutHorizontal) == 0 ) {
                mpobjLayout = new QHBoxLayout;
            } else if ( strLayout.compare(clsXMLnode::mscszLayoutVertical) == 0 ) {
                mpobjLayout = new QVBoxLayout;
            }
        }
    

    mpobjLayout is initialised to nullptr in the constructor. mpobjLayout is defined in the class as:

    QLayout* mpobjLayout;
    

    At the end of the node constructor:

        if ( mpobjParent != nullptr ) {
    //Update the parent adding 'this' node to it's child list
            mpobjParent->appendChild(this);
    //Is the parent a group box?
            if ( mpobjParent->cstrGetNodeName().compare(clsCNT::mscszGroupBox) == 0 ) {
    //Yes, does it have a layout?
                QLayout* pobjLayout(mpobjParent->pobjGetLayout());
                if ( pobjLayout != nullptr ) {
    //Yes, add this widget to the parent layout
                    QWidget* pobjWidget(pobjGetWidget());
                    if ( pobjWidget != nullptr ) {
                        pobjLayout->addWidget(pobjWidget);
                    }
                }
            }
        }
    

    For some reason which I don't quite understand I am seeing:
    5ac2d67b-b215-4394-94f5-c098ca6b3c39-image.png
    Why are the radio buttons not in the group box?

    I should add in the group box widget constructor:

        if ( mpobjNode != nullptr ) {
            QLayout* pobjLayout(mpobjNode->pobjGetLayout());
            if ( pobjLayout != nullptr ) {
                setLayout(pobjLayout);
            }
        }
    

  • Lifetime Qt Champion

    Hi,

    For quick debugging purpose you should print the pointer value of each object you test to ensure you are not passing in the else clause unexpectedly.



  • @SGaist , I'm not really sure what or how this would help? I'm checking the pointers everywhere before use.


  • Lifetime Qt Champion

    @SPlatten
    Hi
    What parent do you assign the radio buttons?

    QWidget* pobjWidget(pobjGetWidget());



  • @mrjj , in my XML file:

    <groupbox id="enSEX" eol="true" align="left" layout="vertical" 
    	  dbfield="vcSex">
    	<radiobutton id="rdoM" text="Male" default="true" position="0,0"/>
    	<radiobutton id="rdoF" text="Female" position="1,0"/>
    </groupbox>
    

    Where groupbox results in a QGroupBox being created and each radiobutton results in a QRadioButton.

    In my class constructor for clsQtGroupBox which is derived from QGroupBox I check the node attribute and create a layout if specified:

    QString strLayout(mpobjNode->strGetAttribute(clsXMLnode::mscszAttrLayout));
    if ( strLayout.compare(clsXMLnode::mscszLayoutGrid) == 0 ) {
        mpobjNode->mpobjLayout = new QGridLayout(pParent);
    } else if ( strLayout.compare(clsXMLnode::mscszLayoutHorizontal) == 0 ) {
        mpobjNode->mpobjLayout = new QHBoxLayout(pParent);
    } else if ( strLayout.compare(clsXMLnode::mscszLayoutVertical) == 0 ) {
        mpobjNode->mpobjLayout = new QVBoxLayout(pParent);
    }
    if ( mpobjNode->mpobjLayout != nullptr ) {
        setLayout(mpobjNode->mpobjLayout);
    }
    

    mpobjLayout is initialised to nullptr in the mpobjNode constructor. I've checked the source in debug and each radio button has the QGroupBox as a parent.

    I think this could be the problem as looking at:
    https://doc.qt.io/qt-5/qtwidgets-widgets-groupbox-example.html

    It looks like the parent of the radio buttons should be the layout not the group box.

    After creating the layout I can see that mpobjLayout is not nullptr.

    Calling mpobjLayout->widget() returns nullptr, why?
    Could it be because mpobjLayout is defined as QLayout?

    I thought this should be compatible with QGridLayout, QHBoxLayout and QVBoxLayout since
    QGridLayout is derived from QLayout
    QHBoxLayout and QVBoxLayout are derived from QBoxLayout which is derived from QLayout.


  • Lifetime Qt Champion

    @SPlatten said in Layout, widgets not inside ???:

    QString strLayout(mpobjNode->strGetAttribute(clsXMLnode::mscszAttrLayout));
    if ( strLayout.compare(clsXMLnode::mscszLayoutGrid) == 0 ) {
    mpobjNode->mpobjLayout = new QGridLayout(pParent);
    } else if ( strLayout.compare(clsXMLnode::mscszLayoutHorizontal) == 0 ) {
    mpobjNode->mpobjLayout = new QHBoxLayout(pParent);
    } else if ( strLayout.compare(clsXMLnode::mscszLayoutVertical) == 0 ) {
    mpobjNode->mpobjLayout = new QVBoxLayout(pParent);
    }
    if ( mpobjNode->mpobjLayout != nullptr ) {
    setLayout(mpobjNode->mpobjLayout);
    }

    You know that passing a parent to a layout automatically applies that layout on the parent given ?

    Following the logic of that block of code, you should replace pParent by this and drop the last if.



  • @SGaist , I've modified the source and tested again, still the same result:

    QString strLayout(mpobjNode->strGetAttribute(clsXMLnode::mscszAttrLayout));
    if ( strLayout.isEmpty() != true ) {
        QWidget* pobjWidget(mpobjNode->pobjGetWidget());
        if ( pobjWidget != nullptr ) {
            if ( strLayout.compare(clsXMLnode::mscszLayoutGrid) == 0 ) {
                mpobjNode->mpobjLayout = new QGridLayout(pobjWidget);
            } else if ( strLayout.compare(clsXMLnode::mscszLayoutHorizontal) == 0 ) {
                mpobjNode->mpobjLayout = new QHBoxLayout(pobjWidget);
            } else if ( strLayout.compare(clsXMLnode::mscszLayoutVertical) == 0 ) {
                mpobjNode->mpobjLayout = new QVBoxLayout(pobjWidget);
            }
        }
    }
    

    In the above code:
    this points to the an instance of clsQtGroupBox.
    mpobjNode is a pointer to the XML node, in this case groupbox.
    pobjWidget is a pointer to the instance of QGroupBox.
    mpobjLayout is a pointer to the layout created using the pobjWidget as a parent.

    Later in the code where the radio buttons or other nodes are created and added to parents:

     if ( mpobjParent != nullptr ) {
        bool blnAppend(true);
    //Does the parent node have a layout?
        QLayout* pobjLayout(mpobjParent->pobjGetLayout());
        if ( pobjLayout != nullptr ) {
    //Yes, add this widget to the layout
            QWidget* pobjWidget(pobjGetWidget());
            if ( pobjWidget != nullptr ) {
                pobjLayout->addWidget(pobjWidget);
                blnAppend = false;
            }
        }
    //Update the parent adding 'this' node to it's child list
        mpobjParent->appendChild(this, blnAppend);
    }
    

    this points to an instance of clsQtRadioButton
    mpobjParent is a pointer to the parent clsQtGroupBox
    pobjLayout is a pointer to the layout QLayout created in the previous section.
    pobjWidget is a pointer to QRadioButton widget

    Unfortunately this still results in:
    Screenshot 2021-10-17 at 08.13.40.png


  • Lifetime Qt Champion

    The issue I am seeing here is that your children widgets seems to need to know stuff about their parent. Why ?

    Following a top down approach, you start with the "master" widget that for example is your QGroupBox, add a layout to it, then next step, add the two QRadioButtons one after the other.

    If that group box is inside another widget, then it's not its problem. The positioning within a parent widget's layout or in coordinates is the responsibility of said parent.



  • @SGaist I would just like to point out that in many cases manual layout of widgets saves a lot of development time and the code is perfectly understandable (unless sloppily written). The present-day focus on XML layout is a fad that is wasting a lot of people's time.


  • Moderators

    @Publicnamer said in Layout, widgets not inside ???:

    I would just like to point out that in many cases manual layout of widgets saves a lot of development time and the code is perfectly understandable (unless sloppily written). The present-day focus on XML layout is a fad that is wasting a lot of people's time.

    For small projects, perhaps.

    I, for one, find that a WYSIWYG editor helps me get my GUI up and running faster than manually coding its layouts in C++. And for very large projects, it's helpful to enable a front-end designer and back-end developer to work in parallel.

    Please note that to OP's use-case is not the same as how we typically use XML .ui files in Qt. It is definitely not our "present-day focus".



  • If you want to know if your QRadioButtons are inside our outside your layout, obtain and print the pointers upon creation. At the end of your code, read the widget pointers of your layout and compare them like that:

    for (int i = 0; i < yourLayout->count(); ++i)
    {
      QWidget *widget = gridLayout->itemAt(i)->widget();
      // qdebug or cout the pointer or write it to a vector
    }
    

    That is the only way to figure out if there is a bug in your complex code or a Qt misbehavior.



  • @AxelVienna , I modified my code setting the objectName for each widget I then added:

            if ( pobjWidget != nullptr ) {
    //Set the object name
                QString strID(strGetAttribute(clsXMLnode::mscszAttrID)),
                        strName(mstrName);
                if ( strID.isEmpty() != true ) {
                    strName += ", id: " + strID;
                }
                pobjWidget->setObjectName(strName);
            }
            if ( pobjParent != nullptr && pobjParent->mpobjLayout != nullptr ) {
                pobjParent->mpobjLayout->addWidget(pobjWidget);
                for (int i = 0; i < pobjParent->mpobjLayout->count(); ++i) {
                  QWidget *widget = pobjParent->mpobjLayout->itemAt(i)->widget();
                  QString strWidget(widget->objectName()), strParent(widget->parentWidget()->objectName());
    qDebug() << strWidget << ", parent: " << strParent;
                }
            }
    

    I checked in the debugger and strWidget is exactly what I expected to see, but there is still no difference in the output.

    In the above the output is:

    radiobutton, id: rdoM, parent: groupbox, id: enSEX
    radiobutton, id: rdoF, parent: groupbox, id: enSEX
    

    This is using the XML:

    <groupbox id="enSEX" eol="true" align="left" layout="vertical" 
    		     dbfield="vcSex">
    	<radiobutton id="rdoM" text="Male" default="true" position="0,0"/>
    	<radiobutton id="rdoF" text="Female" position="1,0"/>
    </groupbox>
    

    The debug output looks correct, but the screen still looks the same.



  • As @Publicnamer said, creating an UI fully programmatically takes time and creates fuzz. Your debugging just tells us that two radio buttons are inside a group box. You have to look at the pointers themselves to make sure your layout is really the I’m your group box and the radio buttons are the ones you mean.



  • @AxelVienna , time is what I have, I know the nodes are correct, I used the information on this page as a guide:
    https://doc.qt.io/qt-5/qtwidgets-widgets-groupbox-example.html

        QGroupBox *groupBox = new QGroupBox(tr("Exclusive Radio Buttons"));
    
        QRadioButton *radio1 = new QRadioButton(tr("&Radio button 1"));
        QRadioButton *radio2 = new QRadioButton(tr("R&adio button 2"));
        QRadioButton *radio3 = new QRadioButton(tr("Ra&dio button 3"));
    
        radio1->setChecked(true);
        QVBoxLayout *vbox = new QVBoxLayout;
        vbox->addWidget(radio1);
        vbox->addWidget(radio2);
        vbox->addWidget(radio3);
        vbox->addStretch(1);
        groupBox->setLayout(vbox);
    
        return groupBox;
    }
    

    My clsQtGroupBox is derived from my clsXMLnode class, this class has a member called mpobjLayout which is created when the node has a layout attribute. The group box node has a layout attribute and thats why it has a layout, if the parent of the radio buttons has a layout then they are added to the layout and the layout is set as the layout of the group box. I just can't see how my code differs from the example.

    Each instance of clsXMLnode has a QWidget which is QGroupBox, QRadioButton etc.



  • @SPlatten said in Layout, widgets not inside ???:

    if the parent of the radio buttons has a layout then they are added to the layout

    That may be the problem. What if the parent hasn’t got a layout (yet)? Does your code throw an exception, returns an error or just stops? Or does it place the buttons outside the group box? I tend to believe that your code provokes the behaviour since I have never seen a bug in Qt that fiddles with widget assignments.



  • @AxelVienna , I manage everything, only the nodes I add have widgets and only the widgets I assign a layout have a layout… unless QT is doing something I’m not aware of.



  • A bold statement…. A lot of volunteers have read through your posts, tried to help and advise. If there are reasons to maintain your approach and you can’t find the bug, you have to hire an expert.


  • Lifetime Qt Champion

    @SPlatten said in Layout, widgets not inside ???:

    I just can't see how my code differs from the example.

    Parent handling from child widgets, that's the main difference I already suggested to avoid.



  • @SPlatten said in Layout, widgets not inside ???:

    QGroupBox *groupBox = new QGroupBox(tr("Exclusive Radio Buttons"));
    
    QRadioButton *radio1 = new QRadioButton(tr("&Radio button 1"));
    QRadioButton *radio2 = new QRadioButton(tr("R&adio button 2"));
    QRadioButton *radio3 = new QRadioButton(tr("Ra&dio button 3"));
    
    radio1->setChecked(true);
    QVBoxLayout *vbox = new QVBoxLayout;
    vbox->addWidget(radio1);
    vbox->addWidget(radio2);
    vbox->addWidget(radio3);
    vbox->addStretch(1);
    groupBox->setLayout(vbox);
    
    return groupBox;
    
        auto groupBox = new QGroupBox(tr("Exclusive Radio Buttons"), this );
    
        auto radio1 = new QRadioButton(tr("&Radio button 1"), groupBox);
        auto radio2 = new QRadioButton(tr("R&adio button 2"), groupBox);
        auto radio3 = new QRadioButton(tr("Ra&dio button 3"), groupBox);
    
        auto button_group = new QButtonGroup;
        button_group->addButton(radio1) ; 
        button_group->addButton(radio2) ;
        button_group->addButton(radio3) ;
        button_group->setExclusive( true );
        radio1->setChecked(true);
    
        auto vbox = new QVBoxLayout( groupBox );
        vbox->addWidget(radio1);
        vbox->addWidget(radio2);
        vbox->addWidget(radio3);
        vbox->addStretch(1);
    
        return groupBox;
    


  •     QString group_style_sheet = QString("QGroupBox{border: %1px solid gray;border-radius: %2px;margin-top: %3px;}" )
                                                                             .arg( m_groupBorderThickness )
                                                                            .arg( m_groupBorderRadius )
                                                                            .arg( text_font_size * 1.6 );
    

    Also you may need to set group style sheet to move text to the top of group frame. I do use it. Otherwise, the title text may push the radio buttons out of the group frame. Set minimum height to your group box.
    If you do not want to set border properties, it is OK. But it is better to set margin top which is related to your group font size. Play with font size and parameter 1.6 and you will be able to move the radio buttons into the group frame.



  • @JoeCFD, I'm not sure what you are demonstrating here? The section of code I pasted comes directly from the Qt link, also posted.

    What purpose does the QButtonGroup serve?

    I edited my XML and applied the style:

    <groupbox id="enSEX" eol="true" align="left" layout="vertical" 
    		  dbfield="vcSex" properties="QGroupBox { border-radius: 8px; background-color:#ff0000; };">
    	<radiobutton id="rdoM" text="Male" default="true" position="0,0"/>
    	<radiobutton id="rdoF" text="Female" position="1,0"/>
    </groupbox>
    

    Here is the result:
    Screenshot 2021-10-18 at 20.37.30.png



  • @SGaist , if only I could show you the rest of my code, when I create any widget I pass the parent widget to the constructor that creates the new widget.



  • @SPlatten said in Layout, widgets not inside ???:

    QButtonGroup

    QButtonGroup serves making radio buttons exclusive. It is a common use. Otherwise, you need to handle them. Works for other buttons as well.
    Adding stylesheet with margin-top will help you move the radio buttons into the group box(set some minimum size to the groupbox to accomodate these buttons). I had the same problem as yours before. I solved the issue with stylesheet. Did you notice your title text("Exclusive Radio Buttons") does not show because it is inside the group box. The first radio button is there too.



  • @JoeCFD , thank you, so is this a Qt bug? as the link I posted before doesn't use QButtonGroup ?



  • @SPlatten It is true that that is a bug in the example. You copied it from there. If qbuttongroup is not used, you have to have a slot onButtonClicked to toggle them(messy). Sometimes, you may need it for your app.

    QButtonGroup is very helpful. Now you know how to use it.



  • @JoeCFD , I'll try to describe what I'm working on, I am developing an engine that reads the configuration of what will be contained in a window from an XML set of files. The XML can be edited and reloaded into the engine with no source code changes required, the engine renders the content of the XML file converting it to widgets, as an example:

    <?xml version="1.0" encoding="utf-8"?>
    <form title="Test form" id="frmTest" hspacing="0" vspacing="0" width="480"
    	  height="480" modal="false">
    	<entry control="listwidget" label="Select:" id="enSEL"
    		   cols="24" rows="1" mode="single" excludeFromChangeCheck="true"
    		   resetPropertiesOnChange="true" eol="true">
    		<subscriber signal="itemSelectionChanged" 
    					target="simon2.js@listWidgetHandler"/>		
    		<subscriber signal="currentItemChanged"
    					target="simon2.js@listWidgetChanged"/>		
    	</entry>
    	<entry control="lineedit" label="First name:" id="enFN" eol="true"
    		   cols="24" maxlength="24" accept="alpha_only" dbfield="vcFirstName"/>
    	<entry control="lineedit" label="Surnname:" id="enSN" eol="true"
    		   cols="24" maxlength="24" accept="alpha_only" dbfield="vcSurName"/>
    	<groupbox id="enSEX" eol="true" align="left" layout="vertical" 
    			  dbfield="vcSex" properties="QGroupBox { border-radius: 8px; background-color:#ff0000; }">
    		<radiobutton id="rdoM" text="Male" default="true" position="0,0"/>
    		<radiobutton id="rdoF" text="Female" position="1,0"/>
    	</groupbox>
    	<entry control="checkbox" label="Employed:" id="enEmp" eol="true"
    		  dbfield="intEmployed"/>
    	<entry control="textedit" label="Address:" id="enADR" eol="true"
    		   maxlength="256" accept="alpha_numeric" cols="24" rows="5"
    		   dbfield="vcAddress"/>
    	<groupbox id="enButtons" eol="true" align="right" layout="horizontal">		   
    		<button id="btnApply" api="applyChanges">
    			<subscriber signal="clicked" target="simon2.js@applyButton"/>
    		</button>
    		<button id="btnUndo" api="undoChanges"/>
    		<button id="btnOK" api="submitAndClose"/>	
    	</groupbox>			
    	<on saveChanges="Save changes before changing selection?"/>
    	<on setup="simon2.js@setupForm"/>
    </form>
    

    I'm still having problems in getting the layout and groupbox to work properly, now I am getting a problem where after setting the layout, the code jumps into QWidgetRepaintManager::removeDirtyWidget.

    This happens immediately after I call setLayout on the QGroupBox widget.


  • Lifetime Qt Champion

    Are you giving a parent to the layout before calling setLayout ?



  • @SPlatten Good stuff. Can you please show your code for building layout? XML file has only properties of widgets and can not tell why layout goes wrong.

    A good practice for debugging is to keep a small GUI case with ui file generated from qt designer and then you compile this case. From ui_*** file created in build, you can see how widgets are laid out. In this way, you can save a lot of time. I believe your time worths some good money.



  • @JoeCFD , the issue I have now is that I've created a mock up using Qt Creator and in this I added a QGroupBox, then into this I added a QVBoxLayout then added three QRadioButtons, I then examined the document as XML and everything looked fine, when I build and ran it also looked fine.

    However I'm having difficulty replicating this, I have a QGroupBox, I've created a layout and used setLayout on the QGroupBox widget, so far so good....but now I want to set the parent to the layout but can't, because the layouts are not derived from QWidget and calling ->widget() on the layout returns nullptr. I want to use the layout like a widget so I can add other widgets to it using the layout as a parent.


  • Lifetime Qt Champion

    @SPlatten said in Layout, widgets not inside ???:

    I want to use the layout like a widget so I can add other widgets to it using the layout as a parent.

    You can't. A layout is not QWidget. And I'm wondering why you want to do this? There is already a simple way to add a widget to a layout.



  • @jsulm, I've tried implementing this:

                QLayout* pobjLayout(nullptr);
                if ( pobjParent != nullptr ) {
        //Does the parent have a layout?
                    pobjLayout = pobjParent->pobjGetLayout();
                    if ( pobjLayout != nullptr ) {
        //Yes, clear the pobjParWidget widget
                        pobjParWidget = nullptr;
                    }
                }
                pobjWidget = qobject_cast<QWidget*>(clsCNT::pCreate(this,
                                                                    mstrName,
                                                                    strCSS,
                                                                    slstProperties,
                                                                    pobjParWidget));
                if ( pobjLayout != nullptr ) {
        //Add the widget to the layout
                    pobjLayout->addWidget(pobjWidget);                
                }
    

    However this doesn't work either, the radio buttons still appear outside of the groupbox and not in the layout, I've single stepped the logic, so the radio button widgets are added to the layout.


  • Lifetime Qt Champion

    @SPlatten said in Layout, widgets not inside ???:

    pobjLayout->addWidget(pobjWidget)

    Is this line executed?
    If it is: to which widget does this layout belong? What is pobjGetLayout() actually doing?



  • @jsulm , yes, it is. I've used setObjectName to assign the layouts and widgets the id's they have in the XML.

    In the above pobjLayout points to a QVBoxLayout and pobjWidget points to a QRadioButton.

    The layout is appended to a QGroupBox via setLayout.



  • @JoeCFD said in Layout, widgets not inside ???:

    QString group_style_sheet = QString("QGroupBox{border: %1px solid gray;border-radius: %2px;margin-top: %3px;}" )
    .arg( m_groupBorderThickness )
    .arg( m_groupBorderRadius )
    .arg( text_font_size * 1.6 );

    override the style sheet of group box in the xml with
    int margin_top = font().pointSize()* 1.6;
    QString group_style_sheet = QString("QGroupBox{border: 2px solid gray;border-radius: 8px;margin-top: %1px;}" ).arg( margin_top );
    You try to hardcode it and see if it works.



  • @JoeCFD , thank you appreciated, why isn't this kind of thing required when positioning and using Qt Creator? This is the XML copied from the UI file which works perfectly.

       <widget class="QGroupBox" name="groupBox">
        <property name="geometry">
         <rect>
          <x>120</x>
          <y>170</y>
          <width>301</width>
          <height>201</height>
         </rect>
        </property>
        <property name="title">
         <string>GroupBox</string>
        </property>
        <widget class="QWidget" name="verticalLayoutWidget">
         <property name="geometry">
          <rect>
           <x>9</x>
           <y>29</y>
           <width>291</width>
           <height>161</height>
          </rect>
         </property>
         <layout class="QVBoxLayout" name="verticalLayout">
          <item>
           <widget class="QRadioButton" name="Radio1">
            <property name="text">
             <string>Radio1</string>
            </property>
           </widget>
          </item>
          <item>
           <widget class="QRadioButton" name="Radio2">
            <property name="text">
             <string>Radio2</string>
            </property>
           </widget>
          </item>
          <item>
           <widget class="QRadioButton" name="Radio3">
            <property name="text">
             <string>Radio3</string>
            </property>
           </widget>
          </item>
         </layout>
        </widget>
       </widget>
      </widget>
     </widget>
    

    No sign of any styles or positioning, I'm now trying to reverse the logic to see where the difference is.

    This is what I found in the debugger looking at how the above XML appears:
    Screenshot 2021-10-20 at 18.06.21.png
    What I don't understand is what is **[0] "verticalLayout" as a child ?

    Drill down a bit more into this layout:
    Screenshot 2021-10-20 at 18.25.22.png
    It appears that the groupBox has one child which I agree with and expect verticalLayoutWidget, the layout has 4 children which I didn't expect:

    • verticalLayout
    • Radio1
    • Radio2
    • Radio3

    What is verticalLayout and where did it come from, it has no children, it isn't in the XML layout ?

    Just to clarify, just in case the screenshot isn't clear it shows:

    groupBox
        verticalLayout
            verticalLayoutWidget
            Radio1
            Radio2
            Radio3
    

    Its verticalLayoutWidget that is the mystery...

    Another edit, looked again at the XML and it does match the debugger screenshot. It looks like there is a fiddle in that the first widget is not the QVBoxLayout but a Widget called "verticalLayoutWidget".



  • @SPlatten group box has a layout for three radio buttons and is a child as well. In total, it has 4 children.



  • @JoeCFD, please see edit, bit at the bottom.



  • @SPlatten You created a verticalLayoutWidget inside a group box which has 4 children:
    verticalLayout
    radio1
    radio2
    radio3

    verticalLayoutWidget is not needed. the parent of verticalLayoutWidget is groupBox.



  • @JoeCFD , to repeat what I did:

    • Dragged Group Box from Containers palette and dropped onto centralWidget
    • Dragged Vertical Layout from Layouts palette and dropped onto Group Box
    • Dragged Radio Button from Buttons palette and dropped onto Vertical Layout
    • Dragged Radio Button from Buttons palette and dropped onto Vertical Layout
    • Dragged Radio Button from Buttons palette and dropped onto Vertical Layout
    • Edited text attribute for each control

    Thats it, one layout not two. Take a look at the XML I posted, its pretty clear and its the actual elements that are generated from this XML that I'm questioning.



  • @JoeCFD
    if there is no title for the group, set top margin to 0
    QString group_style_sheet = QString("QGroupBox{border: 2px solid gray;border-radius: 8px;margin-top: 0px;}" );


Log in to reply