Clicking off of an element does not update Inspector

• Sep 7, 2018 - 15:33
Reported version
3.0
Type
Functional
Severity
S2 - Critical
Status
closed
Project

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 8035689

All elements impacted with this issue.
(maybe somewhere related to #275919: Crash when changing stacking order value after exiting edit mode )?

Steps:
1) Default "Intitled" score
2) Select a rest
3) In Inspector: Untick 'Visible"
4) Click on an empty space onto the score
5) Untick "Automatic placement"

Result: crash

See:

placement.gif


Comments

Title Crash by disabling automatic placement of invisible elements Crash when disabling automatic placement of invisible elements

If you select the rest after you make it invisible, there will be no crash. So, the core problem is not placement of the invisible elements, but changing properties of not selected (and probably not existing) elements.

Indeed. Deselecting an element should clear the Inspector window, but it does not. This is a direct result of https://github.com/musescore/MuseScore/pull/3881 which was intended to fix #275099: Panning screen with mouse shouldn't drop selection, which was not a bug anyway, since pressing Ctrl while panning the screen prevents the selection from being dropped. I recommend that we revert the changes from that PR and change the status of #275099 to "by design".

In reply to by mattmcclinch

I don't think panning with Ctrl is intuitive. I mentioned the scenario everyone uses for navigation. Also, don't you think it is strange that panning doesn't drop selection with Ctrl pressed, but does drop without pressing Ctrl.

UPD: moreover, middle button click can even selects measures, notes which is not correct.

Previous behaviour in MuseScore 2, when dragging the screen without holding Ctrl, has been to pan the score without dropping selection. It shouldn't now be that panning without Ctrl drops any selection - that just seems unintuitive to me.