Function panel buttons not working in 3.60.1

Hello,

please, what version of Android do you have?

Can you tell me what exact add-ons and app doesn't respond?

Thank you.

Zdenek, Locus team

My apologies - I had added a dashboard button to the top right corner that although greyed out must have been stealing the input.

Actually, there is a problem here...

I moved the Add Point dashboard button elsewhere but then noticed that touching the screen to pan the map wouldn't work if the original touch was anywhere nearby the greyed out button as I'm not recording a track, I guess. Could the dashboard button's input be completely disabled if greyed out? Also, differentiate between a hold and drag from a tap?

I then moved the button to the bottom left whereupon the target location button no longer worked when the bottom panel was unhidden by a double-tap. The bottom panel is clearly on top of the dashboard button so should receive the input.

Cheers

Hello,

I am sorry, but can you send me a screenshot?

I am not sure what are you trying to do.

Thank you for the clarification.

Zdenek, Locus team

Hi

I made a video showing taps and swipes:

https://drive.google.com/file/d/12L0Fn8ij4A3Xvhf7pS4MkP8VaWv8ft6R/view?usp=drivesdk

Hope it helps.

Hello,

I am so sorry for the late reply. We noticed some problems with our system and your ticket was lost somewhere.

If I see correctly, the dashboard item you have added is "New waypoint...". This element is clickable, so it "stole" the functions of the buttons below.

Generally, if some of the element of the dashboard is clickable (buttons for track recording) or if tiles have full opacity, then it has more priority than the map or buttons under them.

Hope it helps.

Regards,

Zdenek, Locus team

Hi

I'd forgotten about this so feel free to disregard and close.

Here's my two penneth anyway:

The 'New waypoint' icon is both semi-transparent/disabled at this point and below the right panel and so the panel buttons should have priority.

And whether the icon is disabled or not a swipe is not a tap, so starting a swipe near an icon shouldn't cancel the effect of a swipe, rather a swipe/pinch should be higher priority than a tap.

Cheers

Hello,

we have plans to update the whole dashboard functionality, so we definitely bring some improvements to the behavior of buttons.

But even "inactive", this element is still button. So even if it is unclickable itself, it can't be pressed through.

Obviously, there are some challenges to solve.

Have a nice day.

Zdenek, Locus team