Thanks for the bug report. This should be fixed.
The issue was once another ini file was parsed, the section name insertion point was never reset the correct position when the recursive function returned.
Honestly, I can't believe no one noticed this before, but this isn't the first time something like has happened. I bet most @Include files usually contain measures/variables, and not layered meters with relative positioning.
While this does have a potential to break a few skins (at least visually, maybe even with measures), I would argue that those skins were coded in an incorrect way according to our docs.
Anyway, thanks for all the testing.
-Brian
The issue was once another ini file was parsed, the section name insertion point was never reset the correct position when the recursive function returned.
Honestly, I can't believe no one noticed this before, but this isn't the first time something like has happened. I bet most @Include files usually contain measures/variables, and not layered meters with relative positioning.
While this does have a potential to break a few skins (at least visually, maybe even with measures), I would argue that those skins were coded in an incorrect way according to our docs.
Anyway, thanks for all the testing.
-Brian
Statistics: Posted by Brian — Yesterday, 11:07 pm — Replies 3 — Views 1265
