Project

General

Profile

Actions
Copy link

Bug #2213

closed
JD MV

Wt::WTableView->selectionChanged() signal not sending upon non-standard deselection

Bug #2213: Wt::WTableView->selectionChanged() signal not sending upon non-standard deselection

Added by John Davidson about 13 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Michael Vilsker
Target version:
3.3.1
Start date:
09/14/2013
Due date:
% Done:

0%

Estimated time:

Description

If a user clicks on a column header in a WTableView, thereby deselecting one or more selections made in that table, the selectionChanged() signal does not get sent. It should get sent.
In the forum Koen confirmed this was an oversight and asked me to submit a bug report. Here it is.

KD Updated by Koen Deforche about 13 years ago Actions
Copy link
 #1

  • Status changed from New to InProgress
  • Assignee set to Michael Vilsker
  • Target version set to 3.3.1

Michael,

Whenever selection is changed (also because of resorting and thus after layoutChanged() signal) we need to emit the selectionChanged() signal.

koen

JD Updated by John Davidson about 13 years ago Actions
Copy link
 #2

Also, queryModel->reload() causes selection to be dropped without a selectionChanged()signal getting emitted.

MV Updated by Michael Vilsker about 13 years ago Actions
Copy link
 #3

  • Status changed from InProgress to Resolved

KD Updated by Koen Deforche almost 13 years ago Actions
Copy link
 #4

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: PDF Atom