(Download Full Release Nots & ToDo) as a File)
Here's the major features in APRSISCE6P120525.zip and APRSIS321205225.zip
About version is 2012/05/25 07:50
Application identifier incremented to APWW10 (Windows Desktop) and APWM10 (Windows Mobile)
What's new, you might ask. Well, here's the big topics with more details below.
Load GPX files as overlays on the map
Parse frequency information and display in a new "Frequency Monitor" window.
New !Shriek! method of tagging stations for view filtering. Great for APRS-supported events!
Mic-E Special, Priority, and Emergency highlighting and notifying. You can even transmit a Mic-E-equivalent in your comment.
Nickname-based automatic MultiTracks (New and/or Active)
Here's some details on the big stuff:
See Configure / Overlays / Load GPX File. This will show wpts and trksegs from the file in using the following tags:
<wpt lon=… lat=…>
If name is not present, then the waypoint will be auto-named GPXfff-nn where fff is the loaded file count and nn is the waypoint within the file.
If a <trkpt> or <rtept> has a <name>, <desc>, or <cmt>, additional waypoint objects are created with the appropriate data. (<desc> trumps <cmt> if both are present). (James VE6SRV)
GPX waypoint lables show name, altitude, description, and comment as available.
Don't believe GPS heading if not moving fast enough and don't do Heading pressure if not moved outside of coordinate precision. (Chuck AD4ES)
Support View / FreqSpec and Freq w/Issues to show stations/objects with known QSY frequency.
Added Enable / Frequency Monitor which creates a new window for easier spotting of stations transmitting frequency information, especially for mobile operators. The size of the frequency is governed by Configure / Screen / Speed Font Size. (Fred N7FMH)
Note: I purposely have a very soft and loose parser attempting to identify ANYTHING that might be ANYONE's attempt to define freqeuncy in a comment. This will generate a LOT of false positives, which I will work towards eliminating as they are identified. Machines definitely don't infer things as well as humans do, until someone smarter than them teaches them the nuances. If you notice false frequency positives, OR missed frequency intents, please post the explicit station ID and object owner (if an object) to the list and I'll see about informing the frequency parser.
New View / Shrieks. What's a Shriek, you ask? Check http://en.wikipedia.org/wiki/Exclamation_mark and search for Shriek. Anyway, the SkyWarn Spotter Network requires their users to put !SN! into their comment. APRSISCE/32 now parses any !<nonwhitespace>! from comments and groups up to 32 of them in a View / Shrieks submenu. !Shriek!s are also parsed from nickname comments EVEN if the nickname or comment is not enabled! This allows you to nickname your favorite stations with a !EVENT! comment and then View / Shrieks / !EVENT! to see ONLY those stations! Let me know if there's anything else you can imagine for this one. (BTW, there's a Shriek trace log for debugging, but it's likely to be short-lived).
If nicknames are enabled, and a station has a nickname, and that nickname overrides the comment, then ONLY the comment's Shrieks are used. The comment received from the station will be ignored completly for Shriek purposes.
Extend Nickname-driven Auto-Multitracks: New - Open only when station first appears (but not during posit reload), Active - Ensure open when each packet is received (hard to close), Always - Open on process startup & Active after that.
Support wildcard nicknames that auto-clone when new stations are discovered. A single * wildcard must match either the station ID or any -SSID of that station. A double ** wildcard matches any station starting with those characters. This feature allows auto-application of things like !shriek!s and/or automatic MultiTrack options to new stations without knowing the exact station ID in advance. Note that cloned nicknames show @<wildcard> in the menu and "From: <wildcard>" at the bottom of the configuration dialog. (Fred N7FMH)
Support all kinds of things from http://aprs.org/aprs12/EmergencyCode.txt and general Mic-E status codes from aprs101.pdf pages 43-45.
Support View / Mic-E with counts and defined actions when various stations show up with a status. EMERGENCY will a) send an internal message, b) Ensure a MultiTrack is open (New and Active) c) Flash any window centered on the station, and d) Put a red square around the station on the map. Other statuses do subsets of these, see View / Mic-E for details. Note: Contrary to Bob's recommendations, Because of the number of stations beaconing "Special", it does NOT pop open a centered MultiTrack, but only draws a yellow circle around the station. "Priority" does Message, New, Flash, and Orange and there ARE a FEW stations using it (like W7ADA). Just close the MultiTrack when it appears and it won't happen again until the station ages out or you restart (making the Mic-E status new again). Don't blame me, it's in the spec! Note that Mic-Es are no longer recalled from Saved Posits but are only learned from NEW beacons after a restart.
There's a new Configure / Beacon / Mic-E Notification submenu that lets you easily select one of the !EmergencyCodes! listed at http://aprs.org/aprs12/EmergencyCode.txt. Note that for some reason the 6 "custom" ones are not listed as !Code!s.
New Configure / Mic-E containing "Suppress Notifications" and "Suppress Emergencies Too" which disable their respective intrusive (Message, MultiTrack, and Flash) notifications. Other Mic-E status visibilities (top of window text and colored outline) will remain active regardless of these settings. Eventually you'll be able to configure each status individually, but probably NOT for the upcoming general release. At least we can turn off the interruptions! (Adam KC2ANT)
Expose D700(KISS) and D700(RO+GPS) port types to next general release. (CONVerse and IS-Server are still Development-mode only).
Even though all Server ports are still Development only: Define new "Local Server" that doesn't require (but supports) authentication and filters. Upon connection, behaves like a "b/*" filter was entered which, in APRSISCE/32's filter implementation, delivers ALL packets out to the connection. Incoming packets are ignored. However, if a valid user/pass and filter are supplied, it behaves like an IS-Server port.
Height of an antenna for PHG and DFS is now metricized based on the Configure / Metric / Altitude as it should have been. (By popular vote)
Note: The difference between Metric / Altitude and Metric / Distance is the former is feet vs meters and the latter is miles vs kilometers. For information exchange (or matching up to a GPS string or raw APRS packet), some otherwise-metric-using folks may want altitudes in feet, hence the separate settings for the two.
?APRSO only triggers enabled objects that also have an non-zero interval, not ALL defined objects (Steve G6UIM)
?APRSO will only transmit objects via RF if queried from RF. -IS queries only go out via APRS-IS.
?APRSO queries received over RF simply mark objects for transmission on the normal transmitter thread allowing them to be paced rather than bursted.
Add hourly packet type counters to the APRS-IS OK Pane double-click popup window. (Actually in an earlier release)
Define DsVP as "Davis Vantage Pro" weather stations. (Greg K0GDI)
Suppress NickName'd MultiTrackers from Save MultiTrack question, they'll open when new anyway.
Only open NickName'd MultiTrack-When-New AFTER the packet has been fully processed. This avoids opening at 0,0 and then jumping to the correct location, provided that the first packet heard is a posit.
Added Port SubStatus to APRS-IS OK Pane double-click popup as well as Control-DblClick monitors. This will show the current IP:Port for TCP/IP connections with more to follow for different port types. (Note: ME's station info popup still shows the current APRS-IS connection IP:Port, but this may be removed sometime in the future).
Added incoming connection info (including callsign and filter) to Port SubStatus for IS/Local-Server ports.
If a GridSquare status report provides better or the same ambiguity (estimated based on length of the GridSquare string) as the last known location of a station (regardless of how it was acquired), the station is moved to the GridSquare location. I realized that if you were ONLY transmitting a GridSquare, you'd never move after the first packet! (Alex DH2ID)
Read the nitty gritty details fromDevelopment here