I have a lot of questions that have to do with text panels. For example, why does the notorious <Alpha=#> appear when copying or trying to move a part with written code? Or why when copying code from one craft to another, this very code breaks and/or starts to work incorrectly?
For example, I'm still struggling with making a simulation of turning on the cockpit monitors, it even seems to have worked, but this very "monitor" just sharply turns on when you press 1, which takes you out of the dive.
I admit that I do not know a damn thing about programming and that I will not be able to produce any adequate code, even if I help all the forces and on this I need help or at least advice.
That's basically the reason I decided to ask this question. In this mech I was able to disguise <Alpha=#> with frames, but still the very fact of having these inscriptions is extremely depressing
https://www.simpleplanes.com/a/d282gS/A-M-M-U-001-PPU-Kibo-no-hikari-Pre-Production-Unit
@32 thank you for such a detailed response.
Ok I looked at the build and I think I'm right. As of right now you have a function that basically sets the opacity (alpha) to a certain amount. That's fine, except it cycles the value through a bunch of values that aren't supported. That means it displays the value and tag as part of the label since it thinks that it isn't a real tag. I could create an FT function that basically cycles it from the lowest to the highest supported values, but that stuff is kind of a pain when I'm away from my computer. Also, you have a random tag in one of your labels that just says “<Alpha=#>” you can probably delete that and be fine. I might try figuring out how to fix this, but if you don’t hear from me for a couple days you might want to start working on it yourself since I’ve got a very busy few days coming up.
So I assume you've read the rich text documentation as well as this. the issue with the <Alpha=#> bug isnt something I have encountered, but it looks like a leftover Rich Text tag. That particular tag only supports the values 00, 22, 44, 66, 88, AA, CC, and FF so you probably currently have a value entered into that tag that isn't in the supported format. I’m going to look at your build and see what I can do.
Maybe @32 would know something about this?