Describe the problem
There is this behaviour I see in some windows apps where, when a popup or file/folder picker appears, the parent window that spawned this popup/dialog cannot be interacted with at all until that popup is either closed or has a valid option selected by the user.
I tried to use app_handle.dialog().file().blocking_pick_files() on my frontend buttons, but it immediately makes the entire tauri app be flagged as "not answering". And using the standard pick_files() makes it possible to spawn MULTIPLE file pickers, and user still being able to interact with the main window overall.
Describe the solution you'd like
This would be useful on instances where the app should still run, but not be interactable, for now, the only alternative I see are some workarounds like disabling Pointer-Events, Keyboard shortcuts and such in the whole application until the filePicker is solved.
Some examples to illustrate better what I was looking for in the Tauri library to do.
It is a modal window, blocking other actions in the application until the user closes it.
- If you go in basically any website inside chrome (tested now with Twitter), and click on something that opens a filePicker popup, when you try to click on the browser again, you CANNOT until you solve that filePicker popup. (That's the EXACT behaviour I want to replicate in my apps)
Alternatives considered
No response
Additional context
No response
Describe the problem
There is this behaviour I see in some windows apps where, when a popup or file/folder picker appears, the parent window that spawned this popup/dialog cannot be interacted with at all until that popup is either closed or has a valid option selected by the user.
I tried to use
app_handle.dialog().file().blocking_pick_files()on my frontend buttons, but it immediately makes the entire tauri app be flagged as "not answering". And using the standardpick_files()makes it possible to spawn MULTIPLE file pickers, and user still being able to interact with the main window overall.Describe the solution you'd like
This would be useful on instances where the app should still run, but not be interactable, for now, the only alternative I see are some workarounds like disabling Pointer-Events, Keyboard shortcuts and such in the whole application until the filePicker is solved.
Some examples to illustrate better what I was looking for in the Tauri library to do.
Alternatives considered
No response
Additional context
No response