Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Andrew Heard

Pages: [1] 2 3 ... 24
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 13, 2017, 20:28:59 »
@Andrew Heard : if you start "edit on map" from list of tracks, then why start point is better then some in the middle or in the end? So I see nothing logical on pre-selecting just the first point. Try to start this "edit" directly from the map to see difference.

About via-points - if you add new point during planning, it is not considered as "via point", just a "helping track point". If you wants to create a permanent via-point, try to tap on green dot once again. This creates real via-point that will be kept in track, visible in list of points and also used during navigation for notification or re-calculation.
I am editing track from the map, not a list. I am pointing out the left/ right buttons start differently to existing pro behaviour. Existing behaviour is for tapped point to be selected, and therefore, generally, both buttons are enabled. Beta behaviour is for tapped point to be ignored.

As discussed before there needs to be better distinction between a green icon helping point and its converted blue? Via point. Currently almost impossible to tell the difference - shape, better colour, size?

If I edit this new track on the map I can long-tap to edit/ move the point (not always?), but from waypoint list there is an error message that point can't be edited?

How about long-tap on point to display same menu as tapping Tool button? Would be faster in lots of situations.

Maybe instead of further menu level Edit/insert > select point yet again, the Tool menu has separate items for Move/ Insert/ Delete?

Seems named via point is lost if edited and moved?

Moving, deleting points, a simple operation, just takes far too many taps. Surely long-tap point > menu > Delete? And if undo facility provided then no need for confirming each and every operation.

Each recompute is taking a very long time too. Just with simple test track.

Just a few long-winded thoughts to speed up editing and make more intuitive? Could there be a workflow "conflict" between users with short tracks wanting very precise control over placement of all points, and users with long tracks that rely mostly on compute source, and just want to steer in right direction is iniial route needs broad adjustment?

Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 13, 2017, 16:32:24 »
With the new route planner, when I then Edit on map, the previous and next point buttons are both disabled. Would it be more useful that the first point is selected so the Next point button is enabled? Also regards rubber banding, at present when I add a via point during route planning, it doesn't have any icon displayed in subsequent map editing. If i move a via point, all other non start/ stop/ via points on each side of this via point should be deleted and those one or two track segments be recomputed.

Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 12, 2017, 20:02:22 »
First experience with the new "route planning" screen.
  Visually very nice, good work. What I miss is the possibility of searching. On the old screen, you could go to the menu / search and do not have to search the map manually. This is not a new version.
  The second thing is that there is no notice of the route being lost. Simply click on the left arrow and the scheduled path disappears.
  Selecting "Navigation / Guidance" from the context menu when creating a route will cause the application to
yes, I agree, its an interesting visual improvement, as said there is currently a need to be able to search and access then add existing points into the route. However the bigger picture/ question for me remains the inability to efficiently edit this new route once it id saved. Sure, you can edit point by point, but useless to micromanage such a route if it is 10's km long. There is still no effective rubber banding. And why there should be a distiction in UI between route creation and route editing?

Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 05, 2017, 13:31:08 »
Good day Andrew, 9 weeks trip, very nice, enjoy it!!

Problems: hmm sorry to hear this. If you will want any older version, just tell me. Anyway crash: immediately after crash take a log and send me it once you will be on internet. I have reported every day many crashes ... for example after last 30 days I see in crash console: 9308 crashes ... eh. All these are anyway just some automatic crash reports by Android system
@menion- thanks. 9 weeks in Italy Dolomites. Difficult to provide useful report while touring sorry. Manageable for now.

Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 05, 2017, 09:42:42 »
@menion I am slow to report this, and I cannot provide any useful log, as I am cycle touring for 9 weeks. But for the last few releases I have noticed Locus pro crash a few times, no good reason, not using any new feature, just randomly. Previously #rock solid#. But I don't read of anyone else reporting such an issue. Second, again no good data, but sometimes the map is not repainted, only POI and track. Not even change of zoom level or theme or Locus restart helps, and I have had to restart whole phone.

Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 03, 2017, 16:50:25 »
The new track editing mode has good potential. First feature I note lacking compared to previous version - long tap on back or forward point would move to first or last point.

Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: May 23, 2017, 09:31:11 »
Note weather screen date is wrapping in latest beta:

Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: May 20, 2017, 02:12:54 »
Offtopic in LocusMap context, but good for meteo service comparison:
@poutnikl - not offtopic in that DarkSky and new weather screen is currently beta.

Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: May 19, 2017, 00:04:58 »
Again quite significant difference in min/max temperatures between DarkSky & Meteo data sources (probably nothing can be done but just reduces confidence in DarkSky and means feature won't be used so much):

Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: May 15, 2017, 01:07:58 »
A few more thoughts to save space/ make clearer/ more readable in the new weather screen - refer to attachment (Locus VS Meteo)
  • no need for "C" or "F" after temperature
  • no need for 1 decimal of wind speed
  • no need for red & blue thermometer icons
  • no need for month name
The weather icons eg. raining/ thunder are not so clear, whole icon set could be simplified. When displaying "today" the details always start at midnight (generally well in the past). Would it be better to display details starting from "now"? These ideas a mainly based on comparison with the Meteo app which I feel is more readable/ has a slighter better presentation.

Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: May 14, 2017, 10:15:00 »
I very much like the single tab weather screen. However it immediately crashes for this sequence:
  • tap circle-containing-dot icon
  • tap return button
  • --> boom - "unfortunately Locus Map has stopped"

Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: May 14, 2017, 01:34:29 »
new Beta version
@menion - play store still shows 1/2 day after your forum post.

Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: May 06, 2017, 02:31:00 »
Just looking at the new Weather screen.
A) I don't think 1 decimal digit accuracy for temperature & wind speed is needed or can be justified. The data is not that accurate. My 3 other weather apps only display an integer.
B) The "Today" tab is returned back to by itself when I have selected another tab "Tomorrow" or "Next". Maybe refresh after screen on/ off? Annoying.
C) Personally I'd rather see min/ max temperature on "Today" tab rather than the current temperature
D) I'm not even sure what the temperature in big blue font on the "Tomorrow" tab even means? It's not current/ min/ max/ middle of day/ average?
E) Take a look at the Meteo app for comparison. On the first screen I can instantly see min/ max/ wind/ weather summary for today & 5 more days. The Meteo screen is slightly more compact - hours are integer without unnecessary minutes ":00". Contrast with Locus where that summary data is spread across 3 tabs "Today", "Tomorrow" & "Next". I think the Locus "Next" tab does reveal the details slightly more efficiently than switching back & forth between screens in Meteo.
F) Most important is can the data be trusted. I tried to do a quick comparison of actual data for Milano, Italy between DarkCloud & Meteo. Some figures are wildly different - wind speeds. Which to believe? I think the Locus/ DarkCloud temperatures can't be right - they seem time shifted - maximums at night time! For example Locus maximum temperatures at 23:00 whereas Meteo at more likely 14:00.

Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: May 06, 2017, 01:23:29 »
@Andrew Heard: no worry, there were no changes in BRouter profiles
@menion - good. Thank you. Enjoy your holidays.

Versions / Re: [APP] - version 3.23.+ ( 3. 4. 2017 )
« on: May 03, 2017, 09:39:38 »
@menion - have any Locus internal BRouter profiles changed since Locus 3.19? I ask because I was going to incorporate the Locus special "meta fields" %fastprofile%, %avoid_motorways%, %avoid_toll%, %avoid_unpaved%, %is_wet% into my external BRouter profiles for similar control. I have a copy of the 10 profiles from v3.19. Thanks.

Pages: [1] 2 3 ... 24