http://redmine.emweb.be/http://redmine.emweb.be/favicon.ico?16934085252019-09-10T08:18:45ZRedmineWt - Bug #7230: Wt4, WVBoxLayout->setResizable not working, children not visiblehttp://redmine.emweb.be/issues/7230?journal_id=238172019-09-10T08:18:45ZRoel Standaertroel@emweb.be
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Confirmed</i></li></ul><p>That's interesting. Making a layout resizable should actually make it switch to using <code>JavaScript</code> automatically, since that feature is simply not supported with the flexbox implementation.</p>
Wt - Bug #7230: Wt4, WVBoxLayout->setResizable not working, children not visiblehttp://redmine.emweb.be/issues/7230?journal_id=238292019-09-12T09:51:37ZRoel Standaertroel@emweb.be
<ul></ul><p>I see what's going on:</p>
<ol>
<li> Before the widgets are added, the box layout assumes flex layout implementation</li>
<li> The widgets are added, and will create a flex layout item as their implementation</li>
<li> A row is made resizable, causing the box layout to switch to the JavaScript-based layout implementation, but:</li>
<li> The implementation of the items remains the same, and is not updated to the JavaScript-based layout item implementation</li>
</ol>
<p>The issue does not happen when the JavaScript implementation is set before the widgets are added, or before the layout is added to a container. It is thus dependent on the order in which you do things.</p>
<p>We'll have to figure out how to best solve this.</p>
Wt - Bug #7230: Wt4, WVBoxLayout->setResizable not working, children not visiblehttp://redmine.emweb.be/issues/7230?journal_id=468632022-08-17T15:25:14ZAaron Wrightwright_left@yahoo.com
<ul></ul><p>I ran into this today. It was quite confusing, so I thought I'd leave my vote to get a fix in for this.</p>