lasconic wrote > The font should be the same. Even with the same fonts, a different freetype version might be enough to generate slightly different rasterizations.
> Any idea is welcome, but I would prefer to solve the root cause. Yes, but it is important to detect (and then, if possible, solve) *real* problems. For instance, a different order of the the same (commutative) arithmetic operations may lead to different floating point rounding, which might cause a different grid fitting and make the tests to fail; but there might be no *real* (= evident to the eye) difference (no *real* layout change). Then, my feeling is that a way to have the kind of side-by-side image comparisons as in the sample test run can be VERY useful to speed up the check, but the final judge is better to be a human eye (and a human brain). But this is just my opinion, of course! Maurizio -- View this message in context: http://dev-list.musescore.org/Visual-test-suite-tp7578380p7578389.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
