There is a lot of them: opening almost any dialogue box which would work on the score and cancelling it (=> nothing done) sets the score as dirty.
It has to be something quite deep. I could spend some time chasing it, but probably the core developers (Werner?) can think of the right spot to look at immediately, so I'm leaving it to them.
Even if it does no 'physical' harm to the score, it is not so minor, after all, as it might puzzle the users a fear deal. So, I'm raising its priority to 'normal'; feel free to demote it again if you prefer.
Comments
What do you mean by dirty????
Selecting all doesn't appear to affect the appearance of the score at all on my system??
'Dirty' means there is an impending save.
Ah! In that case I can confirm
On my Windows XP SP3 system
Also if you cancel 'Instruments'.
Anything else?
Using MuseScore 2.0 Nightly Build (0d11f9b) - Mac 10.7.4.
I think there are other things, like 'Text...' (in 'Style' menu) - maybe a check could be done for other things.
Using MuseScore 2.0 Nightly Build (0d11f9b) - Mac 10.7.4.
1. Open score.
2. Click on rest.
3. Press 'Command' and 'G'.
Result: 'No note or figure bass selected' dialogue box appears.
4. 'OK'.
Result: Score becomes dirty.
Using MuseScore 2.0 Nightly Build (74b4a45) - Mac 10.7.4.
There is a lot of them: opening almost any dialogue box which would work on the score and cancelling it (=> nothing done) sets the score as dirty.
It has to be something quite deep. I could spend some time chasing it, but probably the core developers (Werner?) can think of the right spot to look at immediately, so I'm leaving it to them.
Even if it does no 'physical' harm to the score, it is not so minor, after all, as it might puzzle the users a fear deal. So, I'm raising its priority to 'normal'; feel free to demote it again if you prefer.
M.
I think this is now fixed?
Also see this: #3607: Score still marked as "dirty" after save if non-visible change
Using MuseScore 2.0 Nightly Build (65bf911) - Mac 10.7.4.
Apparently fixed in ea8b6e1336
Automatically closed -- issue fixed for 2 weeks with no activity.