more DPI_F-related bugs

With DPI_F set to 1 due to https://musescore.org/en/node/284218, tst_runtests also fails:


[…]
Test exchange-voice-part.script PASS
ChordList::read failed:
changeState NORMAL -> NOTE_ENTRY
changeState NOTE_ENTRY -> NORMAL
ChordList::read failed:
ScoreTestScriptEntry: fail
@101;101
<
@101;101
>
@106;106
<
@106;106
>
Script::execute: operation failed:test score inspector.mscx
Test inspector.script FAIL
ChordList::read failed:
changeState NORMAL -> NOTE_ENTRY
changeState NOTE_ENTRY -> NORMAL
Score::startCmd(): cmd already active
Score::endCmd(): no cmd active
Score::startCmd(): cmd already active
Score::endCmd(): no cmd active
ChordList::read failed:
ScoreTestScriptEntry: fail
@97;97
<
@97;97
>
Script::execute: operation failed:test score mindistance1.mscx
Test mindistance1.script FAIL


The first (inspector.script) seems trivial enough, the factor of five comes into play here, as well.

The second (mindistance1.script) appears to really be a precision loss issue due to the internal DPI change, and I have no idea/suggestion how to handle this best.