<state include="states/j3cub-approach-overlay.xml" n="0"/>
<state include="states/j3cub-parking-overlay.xml" n="1"/>
<state include="states/j3cub-tahoe-overlay.xml" n="2"/>
<state include="states/j3cub-hilltop-overlay.xml" n="3"/>
<state include="states/j3cub-glacier-overlay.xml" n="4"/>
<state include="states/j3cub-mountain-overlay.xml" n="5"/>
frankly, it is a freaking mess to code this up for any non-trivial aircraft (i.e. anything more complex than the ogeL, ufo or c172p) - supporting this properly needs a fair bit of infrastructure which is currently misssing, or you're literally coding up all the missing infrastructure in a highly use-case specific fashion
Seriously, you're messing crap up, quit it, it's not wanted here.
If you can't discuss in a thread without being self-entitled and blaming away - then don't.
So we put this to its grave because we think that developers would not add metadata?
Correction - we know that.
And we put it to the grave for the simple reason that no one is volunteering to shoulder the workload required - and that's including you.
something the community has miserably failed to do.
If you'd just follow your own advice...
I had forgotten about the various states that could be set.
Thorsten - I think you're being overly pessimistic here, and far too negative. After all, you've coded up ways to set up the space shuttle at various stages, including IIRC the ability to save off the current command state.
Users browsing this forum: No registered users and 11 guests