You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 26, 2022. It is now read-only.
During stream, align the measure counter to the slash, so that the numbers do not move horizontally as the player goes through the stream.
During break, just align the measure counter to the center.
The naive solution would require using 3 bitmap text actors instead of one. It is theoretically possible to use one, but that would require an inelegant fix, and is also prone to font issues.
The text was updated successfully, but these errors were encountered:
temporarily settext() to the last string the bmt will be.
e.g. settext to "110/110" if the next stream is 110 measures
local w = self:GetWidth() * self:GetZoom() of the bmt while set to this text
set x() of bmt to GetNotefieldX()*0.5 + w*0.5
settext() back to an empty string
set the bmt back to visible(true)
Repeat this^ for each new stream. Rest counts can simply be center-aligned.
In my head, this should work in base10 systems (which the MeasureCounter uses) given the way most fonts display Arabic numerals (which the MeasureCounter uses).
I think.
This does assume that the MeasureCounter will always have its greatest pixel width at the final measure of stream, so it's inelegant at best, and might not work provided certain, unusual glyphs.
Thanks for telling me about self:GetWidth() and this brainstorm. I believe I can work off of that and create a slightly more elegant solution with only one actor.
During stream, align the measure counter to the slash, so that the numbers do not move horizontally as the player goes through the stream.
During break, just align the measure counter to the center.
The naive solution would require using 3 bitmap text actors instead of one. It is theoretically possible to use one, but that would require an inelegant fix, and is also prone to font issues.
The text was updated successfully, but these errors were encountered: