Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Messages app: Remove virtual back button #1105

Closed
mabuchner opened this issue Dec 16, 2021 · 3 comments
Closed

Messages app: Remove virtual back button #1105

mabuchner opened this issue Dec 16, 2021 · 3 comments

Comments

@mabuchner
Copy link

For me the virtual back button in the messages app is really difficult to activate.

Can't we use a short press of the physical button to go back?

Then we wouldn't have this problem and it would give use more space for the message text.

@gfwilliams
Copy link
Member

Press of the button to go back sounds good - however for quite a few messages I think there will also end up being various buttons for actions at the bottom which we wouldn't really be able to do anything about.

There is already an issue open to make the buttons a bit bigger as well, as I know they are a pain to tap at the moment.

@DDDanny
Copy link
Contributor

DDDanny commented Jan 15, 2022

as I wrote in #1294 the bangle2 touch functions could seriously enrich ueser experience.
So i suggest double-touch for back-action and a new option to hide back-button by default.
msg.negative / msg.positive can be handled with swipe left/right and also an option to hide the buttions and instead e.g. make 10 px on the left red and 1ß px on the right green to show to the enduser that confirm/cancel are availible.

@gfwilliams
Copy link
Member

Just fixed this with 83a849a

Physical button now goes back. While we have the on-screen button for now, tapping the text will now bring you to a bigger, scrollable view of the message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants