by wlbragg » Fri Nov 30, 2018 9:12 pm
I looked through the code and it was fairly simple. I verified one by one that it didn't cause any issues. It was all contained to animation variables and mesh and not deeply embedded.
It's should be all cleaned up.
I agree with Thorsten the blanket approach is just too dangerous. I don't think I would ever do that unless I knew the entire code base and it was still fresh in my mind. In this case it would have been fine, but I had no way to really know that.
As far as changing it at all in internal variables, I somewhat agree, but I can't stand this kind of a mistake and if it is my fault I have a tendency to not be able to let it go, unless it it too extensive. This wasn't one of those cases I don't think, pretty simple. Then again it was a pretty simple task when I made the mistake as well.
It was also in tool tips which had to be cleaned up!
Thanks for bringing it to my attention. Let me know if anyone discovers I missed any of the graphics or tool tips.
The CW mode switch is finished as well.
While I was at it I lined up the caution and warning panel light graphics a bit (forward panel, F7 I think) They should look a little better placed on the grid behind them. If there is one in the aft I didn't do it.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q