We shouldn't write the TranslateTransform property as attached in the TransformGroup, that is a bug because it makes no sense and it is ignored.
We'll see if we can reproduce that situation.

Thanks!
Sorry I can't be of use reproducing it. It's a file we'd had open for a while iterating some design on. I've tried a quick repro and I can't figure out what sequence of events lead to it being emitted.

I feel like there's a second part of the bug with the knowledge that it should be ignored then... what is odd though is that while it's ignored by Studio, both the Studio renderer and our own integration based on 3.2.7 are respecting the transform. Is the bug not only that it appeared, but that it isn't ignored?

When I say that it is ignored is that

<TextBlock.RenderTransform>
  <TransformGroup TranslateTransform.Y="400">
    <ScaleTransform/>
    <SkewTransform/>
    <RotateTransform/>
    <TranslateTransform/>
  </TransformGroup>
</TextBlock.RenderTransform>

is not translating the TextBlock in any way, because that attached property set in TransformGroup has no meaning for the TransformGroup itself.

And both Studio and the NoesisGUI SDK will render that TextBlock without any translation.

There is definitely a bit of weirdness which goes on here with it. Attached is a small sample which replicates the issue on unmodified Studio 0.1.220-beta. The screenshot shows that despite the Render/Layout Transform.Y both showing 0 in studio, there is an offset applied pushing the Text into the Green Area.

What is even stranger is that this behaviour is inconsistent between launches. On roughly half of launches, the text will remain at 0,0. On the others it'll have the (incorrect) transform applied. Restart Studio and reopen the project repeatedly to see the behaviour. We spotted the same inconsistency between launches in the SDK

Screenshot 2025-05-20 220028.png (169,859 bytes)   

Screenshot 2025-05-20 220028.png (169,859 bytes)