Problem summary:
The kSelectionChanged event does not always trigger when selecting TrackItems with Shift+LMB
Customer reported version:
Nuke Studio N/A
Customer reported platform:
N/A
Steps to reproduce:
1) Launch Nuke Studio and open a Sequence that has at least two TrackItems on different Tracks.
2) Open the Script Editor and execute the following code:
from hiero.core import events def selection_printer(event): viewer = hiero.ui.currentViewer() sequence = viewer.player().sequence() timeline_editor = hiero.ui.getTimelineEditor(sequence) selected_trackitems = timeline_editor.selection() n = "\n".join([ti.name() for ti in selected_trackitems]) print(f"selection changed: {len(selected_trackitems)} selected...\n{n}") events.registerInterest("kSelectionChanged", selection_printer)
3) Use Left Mouse Button to select the TrackItem on the highest Track
4) Use Shift+Left Mouse Button to select the TrackItem on the lower Track, and observe how the kSelectionChanged event does not trigger. Then, invert the selection order, and note that kSelectionChanged does trigger:
Expected behavior:
The kSelectionChanged event should always fire whenever selection changes, regardless of the selection method.
Actual behavior:
When a TrackItem is selected with Left Mouse Button and then Shift+LMB is used to select another TrackItem on a lower Track, the kSelectionChanged event does not fire. However, if the TrackItems are selected in the opposite order, the kSelectionChanged event triggers as expected.
The same behavior occurs even if no TrackItems are soft-selected by the Playhead. For example, LMB selecting clipA, and then Shift+LMB selecting clipC still does not trigger kSelectionChanged in the following arrangement:
Workaround:
Instead of using Shift+LMB, Ctrl/Cmd+LMB seems to consistently trigger the kSelectionChanged event. Additonally, LMB+Drag can be used to marquee select the TrackItems, which does trigger kSelectionChanged.
Reproduced by Support in:
Nuke Studio 16.0v3 - Windows 11, macOS 15 Sequoia
Nuke Studio 15.2v1 - Windows 11
Nuke Studio 15.1v8 - Windows 11
Nuke Studio 15.1v2 - Windows 11 -- Regression
Unable to reproduce bug in:
Nuke Studio 15.1v1 - Windows 11
Earliest version tested:
Nuke Studio 15.1v1 - This issue doesn't appear in this version and has regressed
