Author Topic: [APP] - version 3.30.+ ( 15. 3. 2018 )  (Read 24762 times)

Offline 0709

  • Padavan of Locus
  • ***
  • Posts: 269
  • Thanked: 33 times
    • View Profile
  • Device: THL4000 CM12.1 SM-T235 A5.5.1 MI A2 Lite A9
Locus Pro 3.39.2
 

Offline skwal

  • More than Newbie
  • *
  • Posts: 37
  • Thanked: 10 times
    • View Profile
  • Device: xcompact
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #76 on: March 22, 2018, 12:19:38 »

i have on the panel the option
altitude manager

when i clicked it in the past i came direct to pressure where i can calibrate the barometer
when i click in  the newest version i come to setting. and have to click to pressure manuel

can it be fixed?

so no bug and an intention?
 

Offline Bucky Kid

  • Padavan of Locus
  • ***
  • Posts: 304
  • Thanked: 5 times
    • View Profile
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #77 on: March 22, 2018, 13:47:28 »
To menion:
Here's another ugly bug with route planner: opening it on certain track forces Locus close. I'm trying to figure out what's specific with this track that it makes Locus crash.

Record from the error log:
Code: [Select]
03-22 13:42:01.281 17089 17089 E AndroidRuntime: FATAL EXCEPTION: main
03-22 13:42:01.281 17089 17089 E AndroidRuntime: Process: menion.android.locus.pro, PID: 17089
03-22 13:42:01.281 17089 17089 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{menion.android.locus.pro/o.sl}: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2699)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2766)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1507)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6236)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:107)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at java.util.ArrayList.get(ArrayList.java:411)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.azp.ॱ(:78)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.iq.ˊ(:705)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.asamm.locus.maps.utils.selection.MapSelection.ॱ(:2478)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.asamm.locus.maps.utils.selection.MapSelection.ˎ(:2433)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sv.ˎ(:604)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sv.ˎ(:210)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sv.ˊ(:77)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.Ч.ॱ(:166)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.ҫ.ˊ(:129)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.Cz.onCreate(:63)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sl.onCreate(:161)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:6684)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2652)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: ... 10 more
03-22 13:42:01.289  1860  1914 W ActivityManager:   Force finishing activity menion.android.locus.pro/o.sl
03-22 13:42:01.300  1860  1914 W ActivityManager:   Force finishing activity menion.android.locus.pro/com.asamm.locus.basic.MainActivityBasic
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11443
  • Thanked: 317 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #78 on: March 23, 2018, 22:56:26 »
*** BETA version 3.30.2.3 ***
- geocaching users: please check display of listings & images. If all is correctly sized and click on images display device image viewer
- GPS problems? Should be a lot better now
- and many other various changes ;)

@skwal , @Bucky Kid
ah, I've forget to check these two problems, sorry. At start of week, I'll look at it ...
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline michaelbechtold

  • Master of Locus
  • ****
  • Posts: 584
  • Thanked: 32 times
    • View Profile
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #79 on: March 24, 2018, 10:35:37 »
Hi Menion, another answer due from my side: bottom system buttons issue ...
Here are the steps on a device with overlay (!) on screen buttons, like LG G5, Moto ...:
1) enter one of those functions that opo up full screen edit forms, like POI, Track, ...
2) enter an input field - now the on screen keyboard appears
3) type what you like
4) to access the save button, you need to get rid of the keyboard, which implies you have to activate the on screen buttons, press the back key, and WAIIIIT, until the onscreen buttons disappear. Only then you have access to cancel/save button from Locus

When you are in edit mode, you'll see the left arc labeled "Save" on the top of the screen. Baaad idea to tap the arc - your edits are gone.
A logical thing that would resolve this trap as well as the button thing were to put the save/cancel buttons to the top of the edit forms. That works for any device, smoothly.

@michaelbechtold
Michael I'm really sorry, but I still don't get it. On all screens except main, Route planner and Track editor, bottom system buttons should be visible all the time. So what means "you have to wait until the Android buttons disappear again"? They should not disappear!

 

Offline 0709

  • Padavan of Locus
  • ***
  • Posts: 269
  • Thanked: 33 times
    • View Profile
  • Device: THL4000 CM12.1 SM-T235 A5.5.1 MI A2 Lite A9
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #80 on: March 24, 2018, 10:42:40 »
+1
Quote
A logical thing that would resolve this trap as well as the button thing were to put the save/cancel buttons to the top of the edit forms. That works for any device, smoothly.
Locus Pro 3.39.2
 

Offline john_percy

  • Master of Locus
  • ****
  • Posts: 689
  • Thanked: 95 times
    • View Profile
  • Device: MotoG
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #81 on: March 24, 2018, 12:41:32 »
For me (MotoG), the onscreen keyboard covers the Cancel/Save buttons, and all that is required is to dismiss the keyboard before tapping Save or Cancel.
Three stages illustrated below.


 

Offline michaelbechtold

  • Master of Locus
  • ****
  • Posts: 584
  • Thanked: 32 times
    • View Profile
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #82 on: March 24, 2018, 15:02:22 »
TXs for testing, John.
The Moto has the overlay buttons like the G5. But the behaviour I recollected from memory. Obviously wrongly.
On the G5 I did test it step by step. The Overlay buttons I have to get first of all by wiping down, then wait until they disappear.
I saw other Locus forms where the save button IS on the top.
So, let's get consistent and wipe out any dependencies on smartphone brand behavious at the same time.
One strike, two flies :-)
 

Offline Viajero Perdido

  • Apprentice of Locus
  • **
  • Posts: 118
  • Thanked: 13 times
    • View Profile
  • Device: Samsung Galaxy Tab S2 (Android 7), Blackview BV6000s (Android 6), Nexus 7 (2013) for Alpha/Beta testing.
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #83 on: March 24, 2018, 19:05:04 »
*** BETA version 3.30.2.3 ***
- geocaching users: please check display of listings & images. If all is correctly sized and click on images display device image viewer
All looks good; can't tell any difference from Pro.  The rare cache-log image still refuses to load (discussed some time ago), but I seem to remember it was resolved as an image-library problem.  Anyway, that only seems to happen rarely.
 

Offline Wolli

  • More than Newbie
  • *
  • Posts: 20
  • Thanked: 3 times
    • View Profile
  • Device: Samsung Galaxy S4 active
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #84 on: March 25, 2018, 11:35:15 »
Hello

even with the new version 3.30.2   the storage of the toolbars: does not work http://wollisgeocaching.de/20180325104843.avi
Functions can be saved, but not apps.
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11443
  • Thanked: 317 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #85 on: March 25, 2018, 12:55:21 »
@michaelbechtold , @john_percy
seems we are finally nothing to moment, my head will understand :).

In older versions, there was a different issue with full-screen mode ... problem was that even after dismissing of the keyboard, bottom panel with system buttons did not appear or appeared, but covered these cancel/save buttons.

What is visible on @john_percy screenshots, is how it should work now! Bottom system panel is always visible, so "back" bottom button is also always visible! Fact, that cancel/save buttons are not visible above keyboard is the problem on my side in how UI is wrote ... needs fix, agree.

Anyway what @michaelbechtold wrote, sound more like a same old problem in older versions. You firstly need to "activate bottom on screens buttons"? The bottom black panel on John's screenshots? Really weird. Is it possible to get a short video from you? Should help me a lot to understand.
Buttons on top is old system I want's to get rid of, so not a solution for me.

@Viajero Perdido
glad to hear it, thanks!
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline 0709

  • Padavan of Locus
  • ***
  • Posts: 269
  • Thanked: 33 times
    • View Profile
  • Device: THL4000 CM12.1 SM-T235 A5.5.1 MI A2 Lite A9
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #86 on: March 25, 2018, 14:54:29 »
To prevent any mistunderstanding, my +1 was only about the UI suggestion ! 
By keeping the cancel/save button visible no need to dismiss the keyboard
(Covered cancel/save button: For a new Locus user, it might be a small pitfall)

« Last Edit: March 25, 2018, 15:03:13 by 0709 »
Locus Pro 3.39.2
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11443
  • Thanked: 317 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #87 on: March 25, 2018, 14:55:21 »
@skwal
problem with Altitude manager fixed, thanks

@Bucky Kid
not sure why this happen to you, anyway crash should be fixed now, thanks

@Wolli
exactly same does not happen to me, but I made small improvement that will hopefully help
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline Wolli

  • More than Newbie
  • *
  • Posts: 20
  • Thanked: 3 times
    • View Profile
  • Device: Samsung Galaxy S4 active
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #88 on: March 27, 2018, 12:22:59 »
@menion

Hi

where I can get the  small improvment ?
 

Offline chrispt

  • Newbie
  • *
  • Posts: 9
    • View Profile
  • Device: Galaxy Note 8
Re: [APP] - version 3.30.+ ( 15. 3. 2018 )
« Reply #89 on: March 28, 2018, 15:05:52 »
So I had a quick question regarding GPS shutdown. I have the option set to shut down GPS when Locus is hidden but it doesn't seem to always do so. Sometimes I'll see it still trying to access location (through the GPS status notification) and I have to go back into Locus and exit out for it to stop using GPS. Am I doing this wrong?