-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Export filename preset is empty when using snap and native dialogs #12867
Comments
I cannot reproduce, its always populated. On stable 0.21.2 and on Windows 11 0.22dev
|
I managed to trace it to The option also causes this behaviour in stable, btw, this is how I figured it out (saw stable doing the same thing, reset profile directory, saw it worked, loaded the configurations in vimdiff and came across that param group (which also includes |
It seems that configuration option has been added 6 years ago; it's there on my old computer, and freecad-daily works with the native gtk dialog without issues; there are 2 major differences between the computers: ubuntu release (old one is 22.04, this one is 23.10) and deb (old system) vs snap (this system). Going to try installing the deb tomorrow to see how it does, since the stable appimage won't start (hitting FreeCAD/FreeCAD-Bundle#67). |
tested with the latest freecad-daily deb, the native dialogs work fine there, so the issue seems to be specific to the snap version (and maybe appimage, but I can't test that one) freecad-daily deb
freecad snap, edge channel
|
one more data point, since I figured out where the weekly appimages were (those don't crash with radeon drivers): the weekly appimage seems to simply ignore the parameter and uses the qt file dialog instead of the system one, so the name is filled in correctly. FreeCAD_weekly-builds-36391-2024-03-11-conda-Linux-x86_64-py310.AppImage
If using the native dialogs is in process of being deprecated, I suppose this can be closed (and hopefully help whoever may come across this - removing the parameters mentioned above "fixes" the problem by reverting to the qt file dialog) |
So not reproducible with the latest weekly builds? Can I close this issue? |
reproducible with a tight set of constraints (snap, gnome-based gtk environment, native file dialogs); I asked in the forum if it's a corner case worth pursuing, or native dialogs are being retired anyway
Sent from Proton Mail mobile
…-------- Original Message --------
On Mar 14, 2024, 19:44, Max Wilfinger wrote:
So not reproducible with the latest weekly builds? Can I close this issue?
—
Reply to this email directly, [view it on GitHub](#12867 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AABM4D6GDMJEX7FXVLAQPQLYYHVZ5AVCNFSM6AAAAABEP6OE5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJYGEYDAMZRGY).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I'm using the snap daily as well, and the The file name is not pre-set in my case either when exporting, as per the issue description. For my personal use, having native dialogs is a bigger benefit, though. |
Is there an existing issue for this?
Problem description
I suspect this is a recent breakage - it used to be that the exported filename (when selecting a body and pressing
ctrl+e
, for instance) would be preset to<fcstd-file>-<body-name>
, and the selected output format would add the extension automatically. Right now, the filename field is always empty, and it seems to require the whole name including extension to be typed, every time...Adding the settings keys mentioned at https://wiki.freecad.org/Fine-tuning#Default_export_filename doesn't seem to help.
Full version info
Subproject(s) affected?
None
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: