From: Dominique F. <df...@gm...> - 2016-09-15 12:59:43
|
> Le 15 sept. 2016 à 14:47, Arshia Cont <ars...@an...> a écrit : > > Thank you a million Dominique. > > It seems to work fine. > > The “numDy” and “numDx” parameters on \bar does not seem to be effective when “autoMeasuresNum” is set to “page”. This said, I realize that on some devices the X-Position is out-of-page so I was trying to test this to see if it works but it doesn’t. nothing can escape your vigilance ! you’re right, that’s due to implementation issues (the number is actually displayed by the next bar) However, since the page break location is not supposed to be known, I dont know why (and how) specific settings should be applied to the number when “autoMeasuresNum” is set to “page”. If really needed, I can try to restore the bar specific settings. Can you give more details for the out-of-page issue? (what kind of device? an example?) — Dom > > I see the same behaviour on a fresh compile of GuidoEditor on Mac. > >> On 15 Sep 2016, at 11:51, Dominique Fober <df...@gm...> wrote: >> >> Hi Arshia, >> >> >>> Le 6 sept. 2016 à 12:22, Arshia Cont <ars...@an...> a écrit : >>> >>> Hello Guidoers, >>> >>> Is there a way to force the renderer to generate Measure Numbers at the beginning of rendered “pages” (aka rows)? >> >> That’s done. >> The autoMeasuresNum attribute of \meter supports ‘page’ as value >> e.g. \meter<"2/4", autoMeasuresNum="page”> >> There is a sample code in 'gmn-examples/new-tags-v1.63/measuresNumberingPage.gmn’ >> To get it, you have to update your ‘dev’ branch. >> — >> Dom >> >> >>> >>> Cheers, >>> >>> >>> Arshia >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Guidolib-devel mailing list >>> Gui...@li... >>> https://lists.sourceforge.net/lists/listinfo/guidolib-devel >> > |