Christian Walther

OK, will try running that when I get set up for it. Meanwhile, I am guessing (untested) that separating `id` and `layer` should be this additional commit. (I’ll squash them...

So far, so good. So here is a preliminary fix for the test. A proper fix would be to remove the redundant lines 5+6 in _id.scad_ and generate a new...

Well, looks like that didn’t fix the test. Figuring out why will need to wait until I can run it locally. Probably some stupid mistake.

Alright, I have fixed it. Evidently adding an attribute isn’t as simple as adding a member, it must also be added to the `toString()` output, because that is apparently used...

Thanks for merging, and thanks for the extensions in #4378!

Success! Thanks for the tip. In 3.12.0a1, all binaries return `platform.machine() == 'ARM64'` when run on ARM64 and `platform.machine() == 'AMD64'` when run on AMD64, which is what I would...

Confirmed, these methods both work on all combinations, on both 3.11.0 and 3.12.0a1. Thanks! That will do as a workaround, although of course it would be nicer to have it...

I’m not sure what is _correct_. Maybe before deciding about that one should discuss what is _useful_. I have use cases for wanting to know * code of what architecture(s)...

(To be honest, I’m a bit surprised this `sanitize()` is needed at all. Shouldn’t it be the job of the XML serialization library to correctly encode attributes?)

Some screenshots for clarification: Actual behavior with Windows set to 200%:  Acceptable expected behavior (matching MOULa; taken with Windows set to 100%):  Preferred expected behavior (mockup) – Windows...