Page 1 of 1

Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Fri Jun 01, 2018 10:25 am
by burekbrigada
After evaluating Alpine in real conditions I will write my thoughts ,ideas and suggestions. I'm programmer too, so I will try to suggest ideas which are in line with overall design of AQ, and which should not add too much bloat.

But before anything - request from subject! Without it, using AQ in any field conditions, harder than light hiking is difficult. In real outdoor activity in many cases people do physically hard things, for example they carry equipment, and tired hands are less able to control precisely. And long press on two buttons (gps, compass) has significant effect. . Actually I need disabling long tap only on GPS and Compass buttons, but maybe is easier to add (and maintain) this for all buttons on main toolbar.

Re: Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Mon Jun 04, 2018 2:37 pm
by burekbrigada
even better then disabling them, option for long tap to always display corresponding menu.

Re: Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Tue Jun 05, 2018 2:37 pm
by Psyberia-Support
Hi and sorry for the delay.
I'll add this in next version, using user settings you'll be able to disable long press on the menu items you want. The menu will be displayed instead.
Best regards

Re: Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Mon Jun 18, 2018 11:11 am
by burekbrigada
Is this available in the latest beta? If it is, what I need to write in the user_settings.conf?
BTW, what is preferred way to communicate about beta? I don't see something like beta forum.

Re: Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Mon Jun 18, 2018 12:24 pm
by Psyberia-Support
Hi,
Yes it is, here are the lines for each menus:

Code: Select all

core.submenu.disable_long_press=1
maps.submenu.disable_long_press=1
landmarks.submenu.disable_long_press=1
geolocation.submenu.disable_long_press=1
orientation.submenu.disable_long_press=1
There is no particular places for comments on beta version, you can either do it here, open a new thread in the relevant forum or post here.

Best regards

Re: Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Mon Jun 18, 2018 1:43 pm
by burekbrigada
Thanks! Tried ...working fine :-)
One little remark, if this is not more than 5 minutes to change:
I expected menu to appear before i pull up my finger, as IRC was before (with enabling/disabling gps/compass). But this is so tiny wish, so if it requires any real effort, ignore it

Re: Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Sun Jul 01, 2018 9:07 am
by Psyberia-Support
Hi again,
I've completely disabled the long press (and not replaced it with something else), that's why you have to release you finger before the action triggers (just like a long single tap). I'll have a look if I have time but right now it's terribly missing!
Best regards

Re: Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Thu Jul 05, 2018 5:15 pm
by burekbrigada
In the latest beta I noticed that you have changed behaviour. For compass it's just what is needed :-) but for GPS it is way worse than before :-(
You need to press gps icon twice to get menu, which means screen will be moved to gps position. I'm aware that gps button is special case, but why not just for long press:

Code: Select all

if geolocation.submenu.disable_long_press=1 then
      call ShowMenu()
else
      call DefaultLongPressAction()
end if

Re: Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Sun Jul 08, 2018 5:49 pm
by alexlong
Are there plans to add 5 new user settings items to the official list of user settings?

Code: Select all

core.submenu.disable_long_press=1
maps.submenu.disable_long_press=1
landmarks.submenu.disable_long_press=1
geolocation.submenu.disable_long_press=1
orientation.submenu.disable_long_press=1

Re: Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Mon Aug 06, 2018 3:49 pm
by Psyberia-Support
Hi again and sorry for the delay.
In the latest beta I noticed that you have changed behaviour
I didn't change anything. As requested initially, you can disable the long press action on any or all menu items.
for GPS it is way worse than before
Can you describe me the behavior you have before and after?
but why not just for long press
You requested to disable long press, it's what I did. But I don't understand why you want to display the menu with a long action while you can do it with a simple (fast or slow) tap!

@Alex: done!

Re: Disable Long tap on main toolbar buttons - user_settings.conf

Posted: Tue Aug 07, 2018 4:28 am
by burekbrigada
for GPS it is way worse than before
Psyberia-Support wrote: Mon Aug 06, 2018 3:49 pmCan you describe me the behavior you have before and after?
After the first changed version, long tap [sort of] was still available and it called the menu. After last update no way to call menu, except moving first to gps position, then long tap [again,sort of] or ordinary fast tap.

You requested to disable long press, it's what I did.
Yes, and I'm really thankful because it was a real deal breaker for me. But then, you said and implemented :-) this:
Psyberia-Support wrote: Tue Jun 05, 2018 2:37 pm I'll add this in next version, using user settings you'll be able to disable long press on the menu items you want. The menu will be displayed
which was even better.
But I don't understand why you want to display the menu with a long action while you can do it with a simple (fast or slow) tap!
Only when display is snapped to GPS position! With behavior form previous beta, menu was available from any position.
Actually, I was satisfied with previous version. I made a remark about cosmetic thing: "sort of long tap", because it was not ordinary long tap, but action [displaying a menu] fired after releasing finger after long tap. You described why app behaved so:
Psyberia-Support wrote: Sun Jul 01, 2018 9:07 am I've completely disabled the long press (and not replaced it with something else), that's why you have to release you finger before the action triggers (just like a long single tap). I'll have a look if I have time but right now it's terribly missing!