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

✏️ [ FEAT REQ ] send immediately #35

Open
Turhvjbufv opened this issue Dec 11, 2023 · 6 comments
Open

✏️ [ FEAT REQ ] send immediately #35

Turhvjbufv opened this issue Dec 11, 2023 · 6 comments
Labels
enhancement New feature or request

Comments

@Turhvjbufv
Copy link

Is your feature request related to a problem? If so, please describe the problem.
A clear and concise description of what the problem is. Send after x seconds is nice since you can cancel a message, but it's a long time if you're talking to someone actively(or maybe add a 2 seconds or 1 second to the options in delayed sending)

Describe the feature you'd like
A clear and concise description of what you want to happen.
An option to add another button next to the cancel button that will allow the user to press it to immediately send the message
Additional context
Add any other context or screenshots about the feature request here.

@Turhvjbufv Turhvjbufv added the enhancement New feature or request label Dec 11, 2023
@octoshrimpy
Copy link
Owner

I like this idea!

@gavine99
Copy link
Contributor

anyone have any user interface ideas to achieve this in a pleasant fashion?
a separate 'send immediate' button next to the timedown/cancel button?
how about the timedown/cancel button gets moved to the far-left of the screen and a new 'send immediate' button goes where the current timedown/cancel button is? (because cancel actions usually float left of ok/yes/continue actions).
maybe also make the 'send immediate' button require a long press to avoid whoopsie-touches ??

@Turhvjbufv
Copy link
Author

anyone have any user interface ideas to achieve this in a pleasant fashion?
a separate 'send immediate' button next to the timedown/cancel button?
how about the timedown/cancel button gets moved to the far-left of the screen and a new 'send immediate' button goes where the current timedown/cancel button is? (because cancel actions usually float left of ok/yes/continue actions).
maybe also make the 'send immediate' button require a long press to avoid whoopsie-touches ??

Yes
Also yes as it will look nicer, but will probably "break" user memory for a while( I think long term it's the option to go with)
An option in settings to toggle between long press and short press would be nice

@gavine99
Copy link
Contributor

gavine99 commented Jan 19, 2025

Thanks for your feedback!

please see pull request #221

I don't normally use delayed sending but during my testing i found that having the cancel button always far-left made it super quick to get into a muscle memory action to click it because it's now always in the same spot no matter how large or small the body text.

i haven't added the global setting because less settings is almost always better :) the extra time for a long press is barely noticeable but definitely protects against accidental touches. for sure, after you and others are able to use the new feature, if the long press proves troublesome, it can be changed to a short press.

@Ilithy
Copy link
Contributor

Ilithy commented Jan 24, 2025

Hi;
What do you think about gestures instead of buttons? This would clean up the interface of the two buttons, and the user would have the ability to configure which swipe gesture (left or right) does what, delete, send immediately, cancel sending...

@Turhvjbufv
Copy link
Author

Hi;
What do you think about gestures instead of buttons? This would clean up the interface of the two buttons, and the user would have the ability to configure which swipe gesture (left or right) does what, delete, send immediately, cancel sending...

It's being discussed in the pr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

4 participants