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

FEATURE REQUEST: Persistent FlashMessage #253

Open
ice-cap0 opened this issue Jun 29, 2023 · 4 comments · May be fixed by #260
Open

FEATURE REQUEST: Persistent FlashMessage #253

ice-cap0 opened this issue Jun 29, 2023 · 4 comments · May be fixed by #260

Comments

@ice-cap0
Copy link

Great lib.

autoHide: false | true both still allow the user to dismiss FlashMessage.

It would be great if we could also prevent the user from dismissing FlashMessage.

Is this doable with the current API?

@ice-cap0
Copy link
Author

ice-cap0 commented Jun 29, 2023

Temp hack:

const recurShow = () =>
  showMessage({
    ...
    onHide: () => recurShow(),
  });
recurShow();

@lucasferreira
Copy link
Owner

Hi @shawarmaz,

I this case how user could dismiss the message? It will be always fixed at the top of the app? The only way to close will be if programmatically hide then?

@ice-cap0
Copy link
Author

ice-cap0 commented Aug 9, 2023

Yes, programmatically.

Use cases are: Network Disconnected, Active Voice/Video Call, Recording Voice Memo, Tracking Location, and many more related to state rather than notifications

Opens up a whole slew of possibilities, making it no longer just a toast/message, but an "in-app status-bar".

Would be feature complete if it could push the entire app down as well, rather than zindexing over the app, a-la-Whatsapp, Discord, iOS Voice memos, Uber Driver, etc

@PivaRos PivaRos linked a pull request Aug 17, 2023 that will close this issue
@PivaRos
Copy link

PivaRos commented Aug 17, 2023

[shawarmaz] here you go, happy to help (:

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

Successfully merging a pull request may close this issue.

3 participants