Configure Preferences

This tab of the Configure dialog specifies user preferences for YAAC.

The options that can be changed here are:

• The fonts that will be used for tabular displays and where a monospaced font would align the text more readably.
• The units of distance (and speed) that will be used in the various tables and displays in the application.
• The units of temperature, pressure, and weight that will be used in the various tables and displays in the application. Note that HPa (hectopascals) are the same as mbar (millibars).
• Specify whether unlabeled and/or untyped OpenStreetMap data should be rendered at close zoom levels. Typically, these are building outlines with no identification of the purpose or name of the building. To render such data, the map tiles must be downloaded after enabling this option, so as to download the additional map data; if this option is not selected, the additional map data will not be downloaded and old copies of the data will be deleted.
• Specify whether OpenStreetMap labels should be displayed in English if the default language of the label is some other language and an English translation is available.
• Choose the format for displaying latitude and longitude values.
• Choose whether the memory usage monitor should be displayed on the toolbar of the map window (not seen by default). This indicates how much memory YAAC is consuming and how much of the consumed memory is actually in use. The associated trashcan button allows the user to force memory garbage collection.
• Specify whether secure encrypted HTTP should be used for web accesses by YAAC or only non-encrypted HTTP. Selecting non-encrypted HTTP should be done if YAAC's only connection to the Internet is via an Amateur Radio TCP/IP network that prohibits encrypted traffic (to comply with regulations). YAAC accesses the following data sources using HTTP and/or HTTPS:

  Data source	HTTP	HTTPS
  YAAC release notes	if HTTPS disabled	yes
  downloading OpenStreetMap tile files	if HTTPS disabled	yes
  USGS digital elevation data	not supported	yes
  US National Weather Service radar overlay	not supported	yes
  upgrading YAAC and plugins	if HTTPS disabled	yes

  The sources that are not supported for unencrypted HTTP will not work if only non-encrypted HTTP is selected, and an appropriate error message will be displayed if you attempt to access them in this mode.
• Specify whether network socket connections (such as to the APRS-IS backbone servers, GPSD, an AGWPE server, or a KISS-over-TCP/IP TNC) can only use Internet Protocol version 4 network addresses. Although IP version 6 has been around for over a decade, some Internet Service Providers still refuse to support it; as such, even though the local computer's operating system may support IPv6, any attempt to connect to a remote service using an IPv6 address will fail because the ISP's routers will not know how to deliver the network packets. This restriction is enabled by default (to prevent rude surprises for users who don't know that their ISP is so backwards), but may be turned off by users who know all socket-connected services they use can be reached by IPv6 (or only have IPv4 addresses to begin with, so it's not an issue). Note that this will not have any affect on webpages on servers with IPv6 addresses, as YAAC does not have any control how URL's are mapped to numeric IP addresses.
• Specify whether YAAC will accept inbound AX.25 connected-mode requests for old-style packet "chat" sessions addressed to the local station. By default, since YAAC is primarily an APRS program, it will reject inbound connected-mode requests, but this can be changed to work similarly to how YAAC can initiate outbound connected-mode sessions to a packet BBS if any RF ports are configured for "raw AX.25".
• Specify whether individual stations and objects marked for tracking should be remembered across YAAC restarts.
• Specify whether YAAC's experimental Mic-E model code should be used if the local position beacon is configured to use Mic-E format packets.
• Specify whether aliases (tactical names) for stations and objects should be remembered across YAAC restarts.
• Whether YAAC should beep (or otherwise alert the user) that a text message addressed to the local station was just received. Note that this does not apply to message groups listed on the General tab of the expert-mode configuration dialog unless the event type is specified as "Message_TO".
• Whether YAAC should flash yellow pointer arrows at a station reporting MicE Special status. YAAC will always flash pointer arrows [red for emergency, orange for priority] at the reporting station for those high priority precedences.
• Whether the map should auto-pan to center a station sending an emergency message.