-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
How to associate xml files with desktop app? #152
Comments
You should be able to associate xml files to the desktop app since latest release (7.9.5). |
What are the options for Enable: Recommended Applications? |
@alderg Ah, ok. There is one other option: "All Applications". I am able to use that to create the association. But after I do that, when I double click on one of the xml files, it only launches the app -- it doesn't actually open the file. I get this screen: |
@AleixDev Works on Windows 10, but not macOS or Linux. |
I can't speak for Mac since I don't have one. About Linux I have no issues creating the association, but if you give me more details (how do you have it installed and in which distro), I can try to reproduce the issue. |
By any chance, is there any plan to switch to an extension specific to draw.io, such as |
Yes. As a workaround you can click on the filename and change it to *.drawio (or any other custom extension). |
I was suggesting the possibility for draw.io to produce by default a |
The original issue for this thread still exists on OSX. Regardless of the extension, once an association is made in OSX, double clicking the file brings the draw.io desktop app to the foreground but doesn't load the file. |
This comment has been minimized.
This comment has been minimized.
Duplicate of jgraph/drawio-desktop#11 |
When I want to edit graph with this app, I hope to click
demo.xml
file rather than lanuch app first and then opendemo.xml
file.the following maybe a solution but not available now:
chrome.exe --profile-directory=Default --app-id=pebppomjfocnoigkeepgbmcifnnlndla demo.xml
The text was updated successfully, but these errors were encountered: