Skip to content
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

No automatic extensions when saving/exporting #311

Closed
sphh opened this issue Feb 25, 2019 · 6 comments
Closed

No automatic extensions when saving/exporting #311

sphh opened this issue Feb 25, 2019 · 6 comments
Labels

Comments

@sphh
Copy link

sphh commented Feb 25, 2019

When I try to save a .dig file the file saving dialog leaves me without any clue about the appropriate filename extension. The same goes for the export dialog.

Would it be possible to append the right extension .dig to the filename if the filetype dropdown menu shows Engauge Document and no file extension is given in the Name: box? The same for the Text CSV and Text TSV exports?

@markummitchell
Copy link
Owner

markummitchell commented Feb 27, 2019

In Linux and Windows the file extension appears when I run it. In OSX the file extension does not appear as shown in the following dialog:

screen shot 2019-02-26 at 9 08 38 pm

However, clicking on the down arrow at the top right brings up a 'Hide Extension' checkbox that you can change. This is standard OSX behavior so it is probably better to not change it.

screen shot 2019-02-26 at 9 11 38 pm

@sphh
Copy link
Author

sphh commented Feb 27, 2019

Linux Mint 19.1
Engauge Digitizer Version 10.11
installed from Linux Mint's flatpack

File > Open...:
image

File > Save as...:
image

File > Export...:
image

@markummitchell
Copy link
Owner

I had assumed the flatpak release was working fine since it tests out fine on the Linux build system. But, I was able to reproduce your problem in Cinnamon Linux. A quick investigation was not enough to identify the problem and solution. This will take more work. Thanks for identifying the problem.

@sphh
Copy link
Author

sphh commented Feb 27, 2019

Thanks for looking into it. If I can help in any way, please feel free to ask!

@markummitchell
Copy link
Owner

This problem seems to be happening outside of Engauge, with a workaround that may require more effort by users than just manually entering filenames themselves. The workaround steps, which switch Engauge from the GTK window manager to the KDE manager, are:

#sudo apt install plasma-discover-flatpak-backend (one time step)
#sudo apt install xdg-desktop-portal-kde (one time step)
#find /usr -name xdg-desktop-portal (find xdg-desktop-portal executable)
#find /usr -name xdg-desktop-portal-kde (find xdg-desktop-portal-kde executable)
#kill xdg-desktop-portal
#kill xdg-desktop-portal-kde
#export XDG_CURRENT_DESKTOP=KDE
#/usr/.../xdg-desktop-portal-kde & (using path from earlier find command)
#/usr/.../xdg-desktop-portal & (using path from earlier find command)
#flatpak run io.github.markummitchell.Engauge_Digitizer

@sphh
Copy link
Author

sphh commented Apr 23, 2019

Thanks for figuring out a workaround. Since flatpak/xdg-desktop-portal-gtk#191 mentions that they might solve the underlying bug, I might wait a bit ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants