http://redmine.emweb.be/http://redmine.emweb.be/favicon.ico?16934085252017-01-05T18:17:21ZRedmineWt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=169822017-01-05T18:17:21ZKayra Akman
<ul><li><strong>File</strong> <a href="/attachments/2415">tableview_test.cpp</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2415/tableview_test.cpp">tableview_test.cpp</a> added</li></ul><p>To reproduce the regression "progressive-bootstrap" should be enabled.</p>
Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=169872017-01-06T18:28:46ZRoel Standaertroel@emweb.be
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>InProgress</i></li><li><strong>Assignee</strong> set to <i>Roel Standaert</i></li></ul><p>It looks like the issue is that the mousedown event on WTableView does not arrive when using progressive bootstrap.</p>
Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=169902017-01-10T16:35:11ZRoel Standaertroel@emweb.be
<ul></ul><p>This is due to the WTableView being rendered as a plain WTable initially. It is never updated to the proper Ajax-based implementation. I'll look into making this transition possible.</p>
Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=169912017-01-10T18:14:50ZRoel Standaertroel@emweb.be
<ul><li><strong>Status</strong> changed from <i>InProgress</i> to <i>Implemented @Emweb</i></li></ul> Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=169942017-01-11T11:56:04ZRoel Standaertroel@emweb.be
<ul><li><strong>Status</strong> changed from <i>Implemented @Emweb</i> to <i>Resolved</i></li></ul> Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=173872017-04-03T10:38:33ZRoel Standaertroel@emweb.be
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul> Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=175482017-04-15T14:04:58ZKayra Akman
<ul><li><strong>File</strong> <a href="/attachments/2480">tab2_table.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2480/tab2_table.png">tab2_table.png</a> added</li></ul><p>Unfortunately this issue is not fixed with Wt 3.3.7. It should be reopened.</p>
<p>The fix for this issue fixed only how WTableView in Tab 1 is rendered, i.e. that it is properly rendered as a WTableView. The WTableView in Tab 2, which is loaded lazily, is still rendered as a table and, therefore, only the clicked() signal is received not selectionChanged(). Note that lazy-loading is the default way of adding a tab to WTabWidget.</p>
<p>The attached screenshot shows the WTableView in Tab 2 of the test application attached to the original report.</p>
<p>Some remarks:</p>
<ul>
<li> Progressive bootstrap is enabled. When it is disabled, WTableView in Tab 2 is rendered properly and selectionChanged() is emitted.</li>
<li> Issue reproducible in a secondary WTabWidget tab which is loaded lazily.</li>
<li> Wt built today (15.04.2017) from the master branch including all the commits after the 3.3.7 release.</li>
</ul>
<p>It is the combination of progressive bootstrap and lazy tab loading that leads to this issue.</p>
Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=175502017-04-18T08:02:27ZKayra Akman
<ul><li><strong>File</strong> <a href="/attachments/2482">tableview_test_2.cpp</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2482/tableview_test_2.cpp">tableview_test_2.cpp</a> added</li></ul><p>Original test code didn't have a WTableView in the second tab. Updated test code attached.</p>
Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=175572017-04-19T09:41:17ZWim Dumonwim@emweb.be
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>InProgress</i></li></ul> Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=179642017-06-14T09:50:58ZRoel Standaertroel@emweb.be
<ul><li><strong>Status</strong> changed from <i>InProgress</i> to <i>Implemented @Emweb</i></li></ul><p>This time it should fully work.</p>
Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=180082017-06-20T16:59:59ZKayra Akman
<ul></ul><p>I have tested with the HEAD of the master branch. Both signals are emitted. Thanks.</p>
Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=180112017-06-21T09:43:30ZRoel Standaertroel@emweb.be
<ul><li><strong>Status</strong> changed from <i>Implemented @Emweb</i> to <i>Resolved</i></li></ul> Wt - Bug #5470: WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6http://redmine.emweb.be/issues/5470?journal_id=184642017-08-16T20:07:05ZRoel Standaertroel@emweb.be
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>