Patch by Daniel Wickstrom, requires a corresponding FLightGear change
to extend the special search function used by this dialog to add
support for a type-prefix.
Big rework of the Adjust LOD ranges dialog to hopefully make it easier to understand, and harder to setup so that models aren't visible by accident.
All range entry is now via sliders.
The sliders are deltas from the previous value.
There is now the option to specifically choose either low detail or high detail AI/MP models. *NOTE* that for models without a fallback index the low detail model will be the blue yellow glider.
There is now clear indication of what happens for the Meters or Pixel modes.
Added a defaults button that will restore a reasonable set of default values.
The properties that were used have been renamed to ensure that sensible defaults will be picked, ideally we'd have a way to migrate things like this but I don't think we do, so this is a reasonable alternative.
Since we mutate the (cached) definition properties on each call to
clone(), we need to reset these values back, or the non-clone()-ed
instance gets confused paths to its input and list widgets.
https://sourceforge.net/p/flightgear/codetickets/2044/
This will only work for valid VORTAC or TACAN stations.
Not all frequencies can be mapped to VOR frequency range. These will be displayed (and entered) without a decimal place to differentiate them.
Realistically 768 pixels is the minimum height for most displays these days, so 500 is a reasonable figure for all displays, and it does make it easier to operate.
- added extra bindings
- reworked the view axis (usually bound to the hat); to move at a better rate.
- trim to elevator position. When selected this will remember the current position and when the joystick is centered it will apply this as the trim. Very useful for carrier approaches; and also it helps to do something that is much easier with loaded controls when you can feel the pressure being reduced by the operations of the trim switch
By setting /sim/model/fallback-model-index, an MP model
can transmit an index into the AI/Aircraft/fallback_models.xml
file which will be used if the aircraft model cannot be found
in other instances Aircraft or AI/Aircraft directories.
GUI and default property for /sim/multiplay/use-detailed-models
to indicated if we prefer to use detailed models from Aircraft (true)
or simpler models from AI (false).
Checklists now support grouping by placing a group of checklists
under a <group> node.
e.g. /sim/checklists/group/checklist
The group can have a <name>, which is used by the checklist dialog
and can be used by other interfaces, such as the FG1000.
- Engines control now use the same axis methods as the flight controls; which allows for these to have an inverted checkbox.
- Change the axis combo boxes to instead show a popup dialog (much like the button config). This is better because the items can be grouped sensibly.
- Changed the way that the "all engines" controls work - the dialog binds these to a "engines/XXXX-all" for which there is a listener in controls.nas which propogates over all engines.
- Added extra bindings to both the buttons and the axis dialogs.
- moved the "None" button to the bottom and renamed it to the more comprehensible "Remove assignment"
Change /sim/multiplay/transmit-only-generics to /sim/multiplay/transmit-filter-property-base, which can be 1 to transmit only generics, or a number greater than 1 to indicate the start index to transmit (e.g. 12000 for new emesary mp bridge properties)
SVG files from Michat on the forum:
Sat Jan 13, 2018 7:36 pm
Me, Michat. I donate the so called garmin1000B.svg file created by me using GPL Inkscape software to FlightGear, the Free Flight Simulator as a present to the flightgear.org. Since now I derived all legal rights to FlightGear via two active developers representatives on this forum topic: Stuart and hooray. They will proceed to upload the file to the FG repository, choosing the best license in order to protect FlightGear from any scammer simulation software, if is possible. Having account the nature of the Flightgear project as public well.
The 13TH of January 2018 in Madrid Spain.
Michat.
- Add new Emesary notification type for NAV/COM data
- Create Update/Publish interfaces using Emesary from properties
- Use interfaces to drive updates to EIS and NAV/COM frequencies
- Change the PageGroupController to a "proper" MFD page
Change fonts; make use of the new feature to allow fonts to be specified using property from dialog xml.
Ensure that all fonts are defined within the style.
Change to use the ports defined in the property tree when connecting from the dialog.
Ensure properties for ports are set to a valid (non zero, not null) value on dialog initialisation.
Add ability to change receive port from dialog firstly to see what it is and secondly to allow multiple fg sessions
As suggested in
<https://sourceforge.net/p/flightgear/mailman/message/35580843/>, use
$FG_HOME/Export rather than $FG_HOME as the default directory for the
file selector dialogs popping up when loading or saving a flightplan
from the route manager dialog. This is because $FG_HOME/Export will not
trigger the "this path is not authorized for writing" refusal added in
280cd523686fbdb175d50417266d2487a8ce67d2, whereas $FG_HOME normally
will.
Since a typical (and suggested) allowed directory for saving flightplans
from the Route Manager dialog is $FG_HOME/Export, it makes sense for the
Load and Save file selection dialogs to open in at least $FG_HOME. And
since $FG_HOME is a hidden dir by default on Unix systems, it is more
user-friendly to display hidden files and dirs in these dialogs as well.
Note: when hidden files/dirs are not displayed, it *is* possible, at
least in the QtFileDialog, to type .fgfs and get inside when
browsing $HOME, but that is probably not obvious to everyone!
The value of "/environment/moonlight" is now automatically set based on the phase of the moon.
Therefore the Moonlight option and slider in the PUI Environment Settings window have been deleted.
Allow multiple, space-separated waypoint specifications to be added to a
route, rather than having to type each one and press the add button
each time.
If no waypoint is selected as the insertion point, show a message
and leave the waypoint input intact, rather than just clearing it.
Update the help label to reflect the change and include a note of how to
create offset waypoints using a radial and distance.
At the suggestion of Gilberto AGOSTINHO, add
button bindings for throttle, mixture and prop
to the joystick configuration dialog.
Specific use-case is users of game-pads, but also
useful to users with a single throttle axis on their
joystick.
This follows from http://thread.gmane.org/gmane.games.flightgear.devel/78650 and
resolves the sign bug https://sourceforge.net/p/flightgear/codetickets/1778/ .
Combined with a matching change to the flightgear repository, this changes the
HUD formats from the current set of 3 (note that the text in brackets is not
shown in the HUD preferences PUI dialog, but is show here for reference):
0) Decimal degrees (37.618890N -122.375000W)
1) Degrees, minutes (37*37.133N -122*22.500W)
2) Degrees, minutes, seconds (37*37 08.0 N -122*22 30.0 W)
to (here the text in brackets is shown in the PUI dialog):
0) DDD format (37.618890N 122.375000W)
1) DMM format (37*37.133'N 122*22.500'W)
2) DMS format (37*37'08.0"N 122*22'30.0"W)
3) Signed DDD format (37.618890 -122.375000)
4) Signed DMM format (37*37.133' -122*22.500')
5) Signed DMS format (37*37'08.0" -122*22'30.0")
6) Zero padded DDD (51.477500N 000.461389W)
7) Zero padded DMM (51*28.650'N 000*27.683'W)
8) Zero padded DMS (51*28'39.0"N 000*27'41.0"W)
9) Trinity House Navigation (51* 28'.650N 000* 27'.683W)
Add valid ranges for day based on selected month and year taking into account leap years.
With this change it should no longer be possible to enter an invalid date.
