-
Notifications
You must be signed in to change notification settings - Fork 214
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
Comments
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: 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. |
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. |
Thanks for looking into it. If I can help in any way, please feel free to ask! |
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) |
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 ... |
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 showsEngauge Document
and no file extension is given in theName:
box? The same for theText CSV
andText TSV
exports?The text was updated successfully, but these errors were encountered: