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

Export filename preset is empty when using snap and native dialogs #12867

Open
2 tasks done
m0n5t3r opened this issue Mar 11, 2024 · 8 comments
Open
2 tasks done

Export filename preset is empty when using snap and native dialogs #12867

m0n5t3r opened this issue Mar 11, 2024 · 8 comments
Labels
Core Issue or PR touches core sections (App, Gui, Base) of FreeCAD Missing: confirmation Missing confirmation from other testers Packaging: AppImage AppImage related Packaging: Snap Snap packaging related UI/UX

Comments

@m0n5t3r
Copy link
Contributor

m0n5t3r commented Mar 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues

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.

Snapshot_2024-03-11_11-41-02
Snapshot_2024-03-11_11-41-49

Full version info

OS: Ubuntu Core 22 (Budgie:GNOME/budgie-desktop)
Word size of FreeCAD: 64-bit
Version: 0.22.0dev.36340 (Git) Snap 952
Build type: Release
Branch: main
Hash: addf08ce6b0df264a47e836e799b6756626f146e
Python 3.10.12, Qt 5.15.10, Coin 4.0.0, Vtk 7.1.1, OCC 7.7.1
Locale: English/United States (en_US)
Installed mods: 
  * fasteners 0.5.14
  * A2plus 0.4.64
  * woodworking 0.21.2.33771

Subproject(s) affected?

None

Anything else?

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@maxwxyz maxwxyz added Core Issue or PR touches core sections (App, Gui, Base) of FreeCAD Missing: confirmation Missing confirmation from other testers UI/UX and removed needs triage labels Mar 11, 2024
@maxwxyz
Copy link
Collaborator

maxwxyz commented Mar 11, 2024

I cannot reproduce, its always populated. On stable 0.21.2 and on

Windows 11 0.22dev

OS: Windows 11 build 22631
Word size of FreeCAD: 64-bit
Version: 0.22.0dev.36277 (Git)
Build type: Release
Branch: main
Hash: 9e1903d46112b3660bf10c6a4537d728101d560b
Python 3.10.13, Qt 5.15.8, Coin 4.0.2, Vtk 9.2.6, OCC 7.6.3
Locale: German/Germany (de_DE)
Installed mods: 
  * 3DfindIT 1.2.0
  * BIM 2021.12.0
  * CfdOF 1.25.2
  * CurvedShapes 1.0.5
  * Curves 0.6.23
  * Defeaturing 1.2.2
  * fasteners 0.5.12
  * FEMbyGEN 2.1.0
  * freecad.gears 1.2.0
  * freecad_metal_workbench 0.0.1
  * OpenDark 2023.12.17
  * sheetmetal 0.4.2

@m0n5t3r
Copy link
Contributor Author

m0n5t3r commented Mar 11, 2024

I managed to trace it to BaseApp/Preferences/Dialog/DontUseNativeDialog, which was set to false; no idea when that preference showed up, it's not present after starting without user.cfg (so forcing default values).

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 DontUseNativeFontDialog, set to true).

@m0n5t3r
Copy link
Contributor Author

m0n5t3r commented Mar 11, 2024

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).

@m0n5t3r
Copy link
Contributor Author

m0n5t3r commented Mar 12, 2024

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
OS: Ubuntu 23.10 (Budgie:GNOME/budgie-desktop)
Word size of FreeCAD: 64-bit
Version: 0.22.0dev.36340 (Git)
Build type: Release
Branch: main
Hash: addf08ce6b0df264a47e836e799b6756626f146e
Python 3.11.6, Qt 5.15.10, Coin 4.0.0, Vtk 9.1.0, OCC 7.6.3
Locale: English/United States (en_US)
freecad snap, edge channel
OS: Ubuntu Core 22 (Budgie:GNOME/budgie-desktop)
Word size of FreeCAD: 64-bit
Version: 0.22.0dev.36392 (Git) Snap 953
Build type: Release
Branch: main
Hash: 9140327832b94ea4325dfcf185e2e68659875e47
Python 3.10.12, Qt 5.15.10, Coin 4.0.0, Vtk 7.1.1, OCC 7.7.1
Locale: English/United States (en_US)
Installed mods: 
  * fasteners 0.5.14
  * A2plus 0.4.64
  * woodworking 0.21.2.33771

@m0n5t3r m0n5t3r changed the title Export filename preset is empty Export filename preset is empty when using snap and native dialogs Mar 12, 2024
@maxwxyz maxwxyz added Packaging: AppImage AppImage related Packaging: Snap Snap packaging related labels Mar 12, 2024
@m0n5t3r
Copy link
Contributor Author

m0n5t3r commented Mar 14, 2024

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
OS: Ubuntu 23.10 (Budgie:GNOME/budgie-desktop)
Word size of FreeCAD: 64-bit
Version: 0.22.0dev.36391 (Git) AppImage
Build type: Release
Branch: main
Hash: 52fffaf50ef8facea2ecfde23d6f1a7d3ad3d80c
Python 3.10.13, Qt 5.15.8, Coin 4.0.2, Vtk 9.2.6, OCC 7.6.3
Locale: English/United States (en_US)
Installed mods: 
  * Curves 0.6.24
  * OpenDark 2023.12.17
  * btl 0.9.9
  * kicadStepUpMod 11.1.0
  * sheetmetal 0.4.3
  * CurvedShapes 1.0.5
  * woodworking 0.21.2.33771

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)

@maxwxyz
Copy link
Collaborator

maxwxyz commented Mar 14, 2024

So not reproducible with the latest weekly builds? Can I close this issue?

@m0n5t3r
Copy link
Contributor Author

m0n5t3r commented Mar 14, 2024 via email

@furgo16
Copy link
Contributor

furgo16 commented Mar 15, 2024

I'm using the snap daily as well, and the BaseApp/Preferences/Dialog/DontUseNativeDialog key was not present. After manually adding it as a bool to BaseApp/Preferences/Dialog/, I can now use native dialogs, which is great. Thanks!

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core Issue or PR touches core sections (App, Gui, Base) of FreeCAD Missing: confirmation Missing confirmation from other testers Packaging: AppImage AppImage related Packaging: Snap Snap packaging related UI/UX
Projects
None yet
Development

No branches or pull requests

3 participants