-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Code Quality: Use protocol launch for open and save file dialogs #15280
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM both for Save and Open, thank you!
I'm working on UI parts for now.
Actually I rolled my Windows back to the latest stable and alias is also working.
Sorry also pushed a small change so that file open/save dialog always spins up a separate Files instance. |
It seems that those dialogs are opened as Files app process, but they probably should be opened in the host window process, such as Notepad or Edge? Is that possible to open as a child process? |
It must be an issue with Windows and after having gone back from Insider to Stable, it just fixed. Maybe that version was malfunctioned. In that case, can we use alias launch as the primary way of launching and use protocol launch as another way of launching in case of failing. I mean grouped in task bar. It currently opens in Files task bar icon. |
Wow, it's amazing! I believe yes! |
Use protocol launch for open and save file dialogs. Reason: on Windows Preview command line launch is currently broken. Files Launcher also uses protocol instead of command line.
@0x5bfa could you check if this works for you?