开云体育

next beta build#202 of YAAC ("Yet Another APRS Client"), created 2024-Sep-07

downloadable from
or

changes and updates include:
1. fix hanging condition in marineports plugin's NMEA0183-over-TCP driver
(library code in core YAAC contributed to the problem).
2. fix some incorrect Javadoc comments in the source code.
3. stop rendering locally-created APRS Objects on the map when displaying
Objects is conditionally suppressed in a YAAC display.
4. fix Edit Filter dialog so that red dot on tabs will appear initially
if a filter on that tab is already restricting the packets and stations
viewed.
5. fix sorting problems on View Local Objects table.
6. conserve storage in imported OSM way files where the Way is identified
as being some sort of amenity type instead of a road or waterway.
7. fix message content filter UI to not place the controls for setting
ambiguity bounds off the screen.
8. fix recognition of some non-standard OSM amenity type values when
importing OSM data into YAAC.
9. add support for the OSM Boundary type "timezone" and the Emergency type
"water_rescue_station". add more OSM amenity types from allowed
value additions to the "man_made" and "building" keys.
10. fix OSM import processing when multiple tags provide amenity type values
and/or the provided values are multiple for a single tag.
11. improve error messages from the JSON message parser when a JSON source
is providing invalid JSON text.
12. fix versioning error for persisted routes in dynamic objects plugin.
UNFORTUNATELY, this is not backwards-compatible, so you will have to
manually delete the old persisted routes from the $HOME/YAAC/routes
directory, and re-load them into YAAC. But now you will not have
issues from further updates to the dynamicobjects plugin.
13. make Ant build.xml file for the ms150utils utility consistent with other
build.xml files in YAAC, having the default target of PACKAGE to build
everything in the module.
14. remove use of the dated.tile.dir override Java property, and allow the
user to select from the GUI older available versions of the imported
OSM data in case of incompatible YAAC structure version or OSM
database vandalism.
14. add logic to allow recreating all window menus when a plugin is installed.
15. add logic to permit removing menu entries for simplified training version
of YAAC (training plugin not yet written).
16. on tile downloading dialogs, don't enable the "refresh all tiles" checkbox
unless there are existing tiles to refresh (preventing user complaints
they never got any tiles downloaded).
17. improve OSM map searches for propagation obstructions.
18. support enlarging the size of the ID field for OSM Ways to prepare for
future growth in way ID numbers, rather than having incompatibility
in the future.
19. fix help lookup code to support possible help file locale plugins.
20. merge Uri DO7HBL's corrections to the German locale translation of
YAAC's UI text.
21. fix OSM rendering of islands in the ocean.
22. fix logic errors in AREDN Objects plugin, fix interconnections view
to not scroll the left-column node names away when scrolling
horizontally. fix race conditions in the AREDN plugin.
23. upgrade Apache compress and POI libraries to latest versions.
24. fix the demo plugin so changing the sequence of slides actually will
update the running demonstration without having to stop the demo
or YAAC itself.

You have to run the upgrade through to completion.

While running your old version of YAAC, choose the menu entry Help->Check for Updates. If it finds a newer version, it will see if your system allows upgrading (it may not, depending on how the old version was installed; perhaps with a different user account such as "root" so the user running YAAC now doesn't have permissions to overwrite it), and, if OK, download the YAAC.zip file. It will then ask you if you want to run the upgrader. If you don't run the upgrader, the YAAC.zip file won't be unpacked to upgrade your existing installation.

When the upgrader is finished, you don't have to let it start the new version of YAAC for you, although you can. I always start the new version manually from a command shell window (not by clicking an icon), so I can see if there are any unexpected error messages.

But the important part is not only downloading the new version, but installing it over the old version.

Hope this helps.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Tim Huffaker <thuffaker@...>
Sent: Monday, September 16, 2024 8:52 PM
To: [email protected]
Subject: Re: [yaac-users] next beta build#202 of YAAC, cerated 2024-Sep-07

Andrew,

Yes, it is bike ride time again. I am trying to upgrade YAAC, and I have an Icon on my desktop to launch YAAC. Unfortunately, the icon does not call up the new software. How can I get the icon to call up the new version of YAAC?

Thank you for your wonder program.

Tim
KM4ESU