2,561
edits
Feature Requests / Proposals / Ideas: Difference between revisions
Jump to navigation
Jump to search
m
Feature Requests / Proposals / Ideas (view source)
Revision as of 16:08, 8 December 2007
, 8 December 2007→Minor Requests
(+ link bugs) |
m (→Minor Requests) |
||
| Line 131: | Line 131: | ||
* add support for non-rectangular hotspots (2D panels) | * add support for non-rectangular hotspots (2D panels) | ||
* currently, hotspots don't seem to work properly if you tilt the panel-we should try to fix this soon | * currently, hotspots don't seem to work properly if you tilt the panel-we should try to fix this soon | ||
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg13570.html Currently, aircraft featuring multiple different startup configurations (i.e. cold/idle) have to be implemented using separate *-set.xml files for each individual situation], however it would make sense to consider a more flexible approach, where all available startup-situations are simply enumerated in the aircraft *-set.xml (i.e. as referenced separate PropertyList-encoded XML files, saved within a corresponding "situation"), so that a "loadxml" command or Nasal script could eventually overwrite the default state with the state from the desired startup situation; later on possibly with an option, allowing users to view all available startup situations and switch at runtime. | |||
=== Intermediate Requests === | === Intermediate Requests === | ||