Started by Menion, April 25, 2022, 16:11:17
0 Members and 1 Guest are viewing this topic.
Quote from: Andrew Heard on April 27, 2022, 08:16:36Quote from: CabrioTourer on April 26, 2022, 22:34:39Interesting new feature to generate shaping points in planner for imported tracks.I guess it's difficult to find a balance between to many or not enough points.@CabrioTourer - check out how http://brouter.de/brouter-web allows total user control of balance of points - Load > Load Track as Route > Tuning > Fuzziness slider control - one side very few shaping points, other side of slider - lots of shaping points - no need for system to compromise because user decides - very nice system IMHO.
Quote from: CabrioTourer on April 26, 2022, 22:34:39Interesting new feature to generate shaping points in planner for imported tracks.I guess it's difficult to find a balance between to many or not enough points.
QuoteAnd if there is a crossing in the distance of x meters. Then Locus sets the point not exactly at 500 meters, but x meters after the intersection.
Quote from: CabrioTourer on April 27, 2022, 15:59:13The problem I see is that Locus creates the points just by guessing.
QuoteSo with this feauture I have no control where and how many shaping points are created.
Quote from: CabrioTourer on April 27, 2022, 15:59:13Maybe I completely misunderstand the usage of this feauture.
Quote from: Menion on April 26, 2022, 08:41:29@joelocthanks for the logs related to the app killing. These are logs directly made by Locus Map right? They are useful for some debugging and testing tasks, but in case, the system kills the app, the app has no chance (no time) to write any info about this crash into these logs. So in case, we try to debug some "crash", it is necessary to create a system log which should be! everything.
Quote from: Andrew Heard on April 29, 2022, 01:26:46Totally agree converting/ promoting an ordinary track point to a Shaping or Via point is unnecessarily tedious at present. It's a very common use case. But we've had this discussion before right ;-(
Quote from: Menion on April 29, 2022, 09:56:31@tapio
Quote from: Menion on April 29, 2022, 09:56:31PiP display: it is possible that panel ratio affects resize options. Anyway, this panel was made mainly for navigation. For this case it is optimized and because of this, it is a little higher. I do not see a sense to increase its size close to the full-screen.
Quote from: Menion on April 29, 2022, 09:56:31Automatic zoom & rotation works for me as well as no glitches as balloni55 wrote above. Sorry, there is not much I may do for now.
Quote from: 0709 on April 27, 2022, 17:37:44.As you the user will be warned immediately ! These trackglitches are now nicely INDICATED by the Locus trackglitch detector tool. (Red circle)
Quote from: Menion on April 29, 2022, 09:56:31@CabrioTourerWhen you create a route in any other web planner, then why do you need to "recalculate" it in the app?
Quote from: CabrioTourer on April 29, 2022, 20:23:14I think I missed something important. How works the "trackglitch detector" ?