Closed
Bug 78283
Opened 23 years ago
Closed 23 years ago
[RFE] onselectionchanged events needed for tree widget
Categories
(Core :: XUL, enhancement)
Tracking
()
CLOSED
INVALID
People
(Reporter: pwilson, Assigned: hyatt)
Details
[RFE} Add onselectionchanged event handler for tree widgets to notify when tree items are added/removed from the selection. This might also apply to other widgets which support multiple selection. Rationale: I am trying to maintain multiple selection in a tree of widgets and a form view of the same widgets. I also need to synchronize a property inspector. The current tree.onselected event only gives the total current selection. This is murder when you need to know when an item is de/selected.
are you using tree or outliner?
Assignee: asa → hyatt
Severity: normal → enhancement
Component: Browser-General → XP Toolkit/Widgets: Trees
QA Contact: doronr → jrgm
Summary: [RFE} onselectionchanged events needed for tree widget → [RFE] onselectionchanged events needed for tree widget
Reporter | ||
Comment 2•23 years ago
|
||
I am using the tree control. I suppose that once mutation events are in I could listen for changes to the "select" attribute. In the meanwhile I clone the selection list and then look for additions and removals.
Assignee | ||
Comment 3•23 years ago
|
||
onselect.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 4•23 years ago
|
||
Not onselect.
Reporter | ||
Comment 5•23 years ago
|
||
I have reconsidered this request. Onselect works fine for most users. It took about 20 lines of code to maintain my own selection list and to compare it with the selectedItems[] list in the onselect event. The differences generate my own selection change events. When mutation events arrive a more direct approch will be available. Please consider this item closed.
Status: RESOLVED → CLOSED
Assignee | ||
Comment 6•23 years ago
|
||
Mutation events are online.
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•