You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the custom layouts I can define buttons on the root level as well as buttons on other pages. So I can create several sub-levels and have a powerful tool for recording e.g. during a bike ride.
However, it is a bit exhausting that I have to press the back button every time to get back to the higher-level page or to the root page. This effort could be avoided.
If I press one too much, the app closes and I have to stop my bike to start the app again.
In most cases, after pressing a tag key, I want to go back to the root layout. Hence my two proposals:
a) Setting option so that after pressing a tag button, a jump is made to the root layout.
b) Attribute on the button in the xml of the custom layout, which can be used to set for each tag button which page is to be jumped to after pressing the button.
Ideally, the attribute can also be specified for a page in general, so that it applies to all tag buttons on the page.
This shouldn't be effective for page buttons, otherwise it won't jump to the corresponding page.
Custom settings from b) should have priority over general settings from a)
The text was updated successfully, but these errors were encountered:
I also think that it should be the default behavior. Maybe we can also add on option in settings like "Go back to main screen when tag added", "Return to root after tag" or so.
Binnette
changed the title
Feature: Automatically jump back to the root page or to another page after pushing a tag button (generally or in the custom layouts)
Go back to layout root page after creating a tag
Nov 23, 2024
In the custom layouts I can define buttons on the root level as well as buttons on other pages. So I can create several sub-levels and have a powerful tool for recording e.g. during a bike ride.
However, it is a bit exhausting that I have to press the back button every time to get back to the higher-level page or to the root page. This effort could be avoided.
If I press one too much, the app closes and I have to stop my bike to start the app again.
In most cases, after pressing a tag key, I want to go back to the root layout. Hence my two proposals:
a) Setting option so that after pressing a tag button, a jump is made to the root layout.
b) Attribute on the button in the xml of the custom layout, which can be used to set for each tag button which page is to be jumped to after pressing the button.
Ideally, the attribute can also be specified for a page in general, so that it applies to all tag buttons on the page.
This shouldn't be effective for page buttons, otherwise it won't jump to the corresponding page.
Custom settings from b) should have priority over general settings from a)
The text was updated successfully, but these errors were encountered: