Notification direct reply #320
Conversation
|
Great job! I like how you handled ongoing notifications, but I feel that for non-ongoing notifications creating a new notification to inform the user that the reply action was handled correctly is a bit too much from a UX point of view (requiring the user to swipe the notification away) while perhaps a toast would do. I know that then this toast would clash with a possible toast triggered by the button action, but still, I feel that button actions with a What do you think? |
Yes, I think you're right. I've pushed a new branch which just removes the notification on receiving a non-ongoing reply. The user can decide themselves what they want to do in the button action. Do you think that's better? |
This allows
termux-notificationactions to use Direct Reply, available since Android N.If you include the special
$REPLYpseudo-variable in the button actions, then on tapping the button in the notification you get a reply prompt. The action script is called back with that in double quotes.If the user presses REPLY and enters "some text" then this will call:
(I guess this will need documentation in termux-api-packages - I'm happy to do that if people want to include the feature.)