- 3.0 nearly completes the implementation of the open-trip toolbar up top.
- Tap the waypoint to drop one in the middle or drag it in place. Tap the routepoint to start a new route with
the routepoint in the middle (or drag it to a starting place). That starts edit mode for that route so more drags of the routepoint tack it on to the end of the route.
- Tap the polygon button to get a 4-point closed route dropped middle of the screen; it is in edit mode. CURRENTLY, dragging a polygon off the toolbar
isn't implemented. When it is, you'll drag that polygon with the crosshairs centered. This polygon drag and quick edit mode will eventually replace the POS area select in the map packs screen.
- Tap 'Done Editing Route' to exit
route editing mode and possibly start another one.
- Edit mode for a route means you tap the routepoint and it is immediately in move mode with a minimal HUD above it (delete, info, cancel buttons). You can also tap a route segment
line to drop a new point there that also starts in move mode.
- Since you didn't know about it until I mentioned it today, if you have a bunch of markers close to each other on the map and tap one, you'll see "Wrong Marker?" in the
HUD. Tap it and you get a list of all the markers in approximately a 1 inch radius from the one you tapped. They are sorted by distance from the original marker tapped. Select the marker you wanted instead and
the HUD for that marker comes up. Handy when trying to pick off a marker located on Patrick's desk along with the other 340 located there.
- 2.8 adds the prototype of a new Open-Trip filter view up top (V) and will have open-trip editing tools (T) later. This opens the possibility
of removing the waypoint drag thingy from the bottom toolbar giving access to the space on the left of it; tighten the spacing and you 'll easily get 4 icons down there. We could
empty the Tools menu into that toolbar (especially because it will eliminate the Tools button). The Smart Paste tool in the tools menu is useful to the users who understand it (and surprisingly,
I've gotten UserVoice messages about it). We could take it out of the Tools menu and put it in its own tab of the Settings dialog. There you can turn it on and off plus there could be scrollable
text/web page explaining how it works. More people may use it that way.
- To have the 'Routes' section of trip details always show, log in with the #! option after your username (or just #! to go anonymous with the debug menu support enabled).
- Added route segment length labels that float on the map.
- Added route/track direction arrows on outside perimeter of route/track. Routes have an arrow for each segment. Tracks scatter arrows approximately every 80 pixels since doing them by
track segment is nuts since segments are like a foot long :)
- Color dialog added coloring the segment length text. Stroke is for the text, fill is for the background; background can be completely transparent.
- The route detail view now includes the segment lengths between the route-points in the table. The length after the last route point is for a closed route that loops back to the first point.
- Improved the Settings/UI dialog; much easier to read; it scrolls with all the options now. In there, you can turn on/off the translucency added with the iOS7 transition. You can
also turn on/off the segment length labels and the track/route direction arrows.
- The rest of these items you may have read if you installed earlier versions of the 2.6 binary:
- Version includes significant UI changes for iOS7. When run under pre-iOS7, it will look mostly like it did before with added translucency here and there. Under iOS7, buttons become blue
text links with no background, which required eliminating some dark backgrounds or they weren't visible. If you don't like the translucency, go to the UI tab of the Settings dialog and you'll find a button there to turn it off.
- The routes section always shows on the project detail page; it includes an 'add' button on the section header to create a new route. The first route-point is dropped center of the map.
THIS IS FOR PREVIEW. 2.6 won't have it since we will only view routes apparently.
- The HUD for a route-point includes the ability to add a new route-point to the route before or after the current point. The added point is automatically put on the midpoint between the
current point and the previous/next point. If there isn't such a point (e.g., new route), it appears at the map center.
- Tapping a track or route shows a 'segment' HUD that highlights the segment (for a track, it can be difficult to see as tracks are composed of apparently billions of small segments). It will give the name
of the owning track/route (tap it to open the detail drawer). It shows the track/route statistics (length, area) as well as how far along the route the tapped point on the segment is.
- The Settings/Colors pane was completely redone and optionally displays a snapshot of the currently displayed map (including composing with the dual view) to give a better idea what the colors look like
on the map.
- The color picker was also redone. It defaults to Simplified mode that sets the stroke color for whatever you are coloring. If what you are coloring also requires a fill (e.g., routes, error radius), that fill
defaults to 20% opacity of the stroke color (this is what I've used for polygons etc in the past). Hit Advanced for the advanced color selection allowing you to set the stroke and fill separately; stroke allows for solid, dotted, or dashed
lines. Line width can be set as well as opacity. The updates are live for things on the map depending on them, but you'll be able to see them for certain on the Settings/Colors view sample.
- Tracks and routes have a color selection for them. Tap the sample line to change it for a specific track/route. You have the option to 'Use Default' to revert to the default set in the Settings/Colors pane.
I have plans for saved color settings in this dialog.
- Route points can be moved; duh.
- I get one crash log daily or every other day for people looking at O'brien county, Iowa. A recent restructure of how Core Data queries are wrapped corrects that.
- Routes are still not pushed to the server. I got the code from Salvador to look at and adapt to my code-base. I also have the special case of splitting routes from the segment HUD (currently not implemented).
- Enhancements to the Debug menu include a Sync All button that does the equivalent to a Sync All button in the trip drawer; this is good for testing background modifications due to the server once you
get the rest of the GUI in a place to test (e.g., get on a waypoint detail view then sync-all to have the server propagate a deletion of that waypoint).
- The TDMB tester built into the Map Packs detail view is now available if you logged in as a tester besides being connected to dev. Works better for QA if they are testing on production and are
suspicious about a TDMB.
- Enhanced the TDMB tester to use Plat metadata while testing a Plat TDMB file. If a tile is missing, it looks to see if there are any metadata markers in that tile. If so, the tile definitely should be
in the TDMB. If metadata isn't available, the missing tiles are reported as warnings since there'd be no way to verify if a missing tile really should be there.
- Added a warning toast message when you pull up the Public Trips view while connected to dev. Those are only accurate and only completely work when connected
- While adding support for favorite route-points, I also added it for tracks and routes. When using a track or route to represent a coordinate, the coordinate of the first trackpoint or
route-point is used. This is the case when you pick a track in the search list for the weather center.
- The markers for routes are smaller since there can be many. These are the default marker images. If you change the image to, say, "outhouse", the regular-size outhouse marker will show.
By default the first and last points of a route are different to make it clear which way the route goes. It is handy, too, because when you view the MyStuff overlay, a route appears as that special route-start marker.
- The current implementation for storing the search trees for TDMB files is fine, but can load more tree data than necessary. I modified the database schema to put the tree data in
another database entity so it is faulted in only when the tree is needed; this will reduce the footprint of the trees in memory when you have hundreds of TDMBs loaded from an SD card. Note that existing databases
that store the trees "in the old way" will continue to work.
- In addition to better lazy-loading of the search tree, I better optimize the tree and pre-qualify a search of the tree so I'll search a tree only if it has a chance of having
our tile. This also keeps the trees for, say, California from being loaded when scrolling around Arizona.
- I rearrange the list of active TDMBs to the most-likely TDMBs to contain our local tiles are at the start of the list.
- All the above improvements to TDMB loading and searching will be mostly invisible to you unless you load 3 SD cards of data on your iPad for testing ;-)
- While the app processes newly-found TDMBs, a new section in the Offline Maps table appears giving you progress on the background scan. The scan of the AZ SD card takes 2 minutes.
If that's a problem, I can improve it. As files are processed, they immediately appear in the table of TDMBs and are live for searching.
- The background scan was greatly improved. The poor-performing ZIP library we got was horribly slow. It would take 29.4 seconds to process the Coconino county Topo tiles. Of that,
only 0.5s was my logic: the rest was processing the zip file. That zip file processing now takes 0.8 seconds.
- Login with '#!' after your username and you'll get a debug menu floating on the bottom of the screen. Tap the button for the menu. Allows for a lot of tile adornment to help testers (especially
with these tdmb issues), and provides a way to drop as many markers as you want in a trip to quickly make huge trips to stress test. That will be expanded to create routes and tracks when I get time.
- Plat data (and benchmark) now display down to more detailed zoom levels; previously it was limited to level 15, but that's not enough for Plat so now I go to 18 before all markers are shown. Note
that this is a blob setting so the setting is in the blob; we control it when we compile blobs which means installed apps don't need code changes as we add more and more meta data marker layers.
- With all the gutting of dualview code, I introduced an optimization that had a bad condition if you chose Bing Streets for the dual view; corrected.
- Extended the debug menu to allow dropping waypoints into the current trip; makes an nxn grid of markers based on your count's square-root; extras beyond n2 are scattered randomly.
The grid is the current map view so you can be in tight or out far for different spreads. You can enter a prefix for the markers. If it is 'pmac', markers will be named 'pmac 102 (Debug)' where the number
is the marker number like we always do, pmac is the prefix, and (Debug) is a suffix I add so the 'delete debug markers' button can pick out just those added via this menu.
- Numbers now include the thousands' separator; this was way more grief in iOS than it should have been...
- Bunches of smaller changes; heck if I can remember them...