WTableView::selectionChanged() signal isn't emitted after upgrading from 3.3.4 to 3.3.6
I use WTableView is with the following selection properties:
WTableView::selectionChanged() used to be emitted with 3.3.4. WTableView::selectionChanged() isn't emitted anymore after upgrading to 3.3.6. I had to connect to WTableView::clicked() signal.
Updated by Kayra Akman almost 6 years ago
Unfortunately this issue is not fixed with Wt 3.3.7. It should be reopened.
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.
The attached screenshot shows the WTableView in Tab 2 of the test application attached to the original report.
- Progressive bootstrap is enabled. When it is disabled, WTableView in Tab 2 is rendered properly and selectionChanged() is emitted.
- Issue reproducible in a secondary WTabWidget tab which is loaded lazily.
- Wt built today (15.04.2017) from the master branch including all the commits after the 3.3.7 release.
It is the combination of progressive bootstrap and lazy tab loading that leads to this issue.