Opened 2 years ago
Last modified 2 years ago
#17467 new bug
FilePanel is not modal
| Reported by: | bitigchi | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Kits/libtracker.so | Version: | R1/beta3 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
It should be modal, therefore it should block any interaction to the parent window until it is dismissed.
Change History (4)
comment:1 by , 2 years ago
| Keywords: | filepanel removed |
|---|
comment:2 by , 2 years ago
I prefer current behavior. It allows for example copy name from window to file dialog.
Application can make file dialog modal if it want. Changing default behavior probably violates documented BeOS API behavior.
comment:3 by , 2 years ago
Modal dialogs should be used when the user is expected to execute a single action. The reason to open the FilePanel is to either open or save a file. Having it non-modal may cause data loss and unexpected behaviours via allowing changes to the parent window. Non-modal open/save panels also increase bug vector significantly as seen in bug #17466, requiring handling special edge cases in code.
comment:4 by , 2 years ago
I guess there is a question as to whether it should be modal by default. Even if it is, it can be made un-modal by applications.
What is the reason for this? I see no benefit to having it be modal, i frequently use this panel for opening new files in e.g Koder and having random Koder windows be blocked simply because I used "open" in one would not be nice at all.