Hm, yes it should work for both widgets (it's actually the same widget/code for both). I wonder if this is some kind of occlusion bug where there's an invisible other widget on top of the track name. Could you run with --developer and hover over the area that is not draggable and post the object name of the widget you're clicking on?
Hm, yes it should work for both widgets (it's actually the same widget/code for both). I wonder if this is some kind of occlusion bug where there's an invisible other widget on top of the track name. Could you run with --developer and hover over the area that is not draggable and post the object name of the widget you're clicking on?