Unable to save SVG in same folder where it was opened from, when the SVG was opened using Javas open method (Windows AppStore version only)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
New
|
Undecided
|
Unassigned |
Bug Description
We have a simple SVG in a tmp folder.
Now we use our Java Application to display said SVG. We let our users open the SVG file with Inkscape from inside the Java Application using the standard open file method.
After the users made some changes to the SVG and saved it, they klick the "accept changes" button in our Java Application, and we refresh the SVG and are able to display the changes they made to the SVG.
This process worked (on Windows 32 and 64 bit) with Version 0.92 and 0.91 so far.
But when a user uses the Version from the Windows AppStore they are unable to overwrite the initial SVG after making some changes to it. It is possible to save the SVG using the save as option and saving it in another folder for example on the desktop.
Is there any explanation why or how the Windows AppStore application is different from the version 0.92 and 0.91 from the website and how it might affect the saving/overwriting process of files.
For now we tell our users to stop using the AppStore version but that's not a good long term solution.
summary: |
Unable to save SVG in same folder where it was opened from, when the SVG - was opened using a Javas open method + was opened using Javas open method |
summary: |
Unable to save SVG in same folder where it was opened from, when the SVG - was opened using Javas open method + was opened using Javas open method (windows AppStore only) |
summary: |
Unable to save SVG in same folder where it was opened from, when the SVG - was opened using Javas open method (windows AppStore only) + was opened using Javas open method (Windows AppStore version only) |
> For now we tell our users to stop using the AppStore version
> but that's not a good long term solution.
Unfortunately it's probably your only option...
Right now I'm the only active Windows developer (and I voted against publishing Inkscape in the Store as I don't have the time to support it)
You might try to contact Microsoft support about it in case it's a general issue with their emulation layer used for Store apps.