fritzing / fritzing-app

Fritzing desktop application
http://fritzing.org
Other
4.02k stars 832 forks source link

Preferences not enabled #3837

Open SciorraR opened 3 years ago

SciorraR commented 3 years ago

Current Behaviour

Text Version 0.9.6 Preferences menu is grayed out.

Operating System: <Mac version 11.4>

Screen Shot 2021-06-06 at 8 29 26 AM Screen Shot 2021-06-06 at 8 30 41 AM
KjellMorgenstern commented 3 years ago

Please use the official build from fritzing.org/download.

SciorraR commented 3 years ago

Definitely a bug, I have the latest build

KjellMorgenstern commented 3 years ago

I retested this after updating to macOs 11.4, still can not reproduce.

Did you upgrade from a previous version of Fritzing? If yes, which one? Maybe some previous files interfere.

Fabri54 commented 3 years ago

I've exactly the same issue. Latest release of Big Sur and latest, official, release of Fritzing. Has anybody found a fix yet? Where should be the preference file?

failiz commented 3 years ago

The same error has been reported in #3829, always on MacOS.

KjellMorgenstern commented 3 years ago

Seemed fixed during tests, but this issue is happening quite random, so we can't close it yet.

sanmaneric commented 2 years ago

This issue persists on Monterey 12.2.1 on Apple Silicon, macOS build 21D62. Fritzing version 0.9.9 downloaded from the official site. Have not updated from a previous version of Fritzing.

failiz commented 2 years ago

I think Kjell fixed it a few weeks ago. It will be fixed in Fritzing 0.9.10, which should be released soon.

makermelissa commented 2 years ago

I'm still experiencing this with the latest code. As a workaround, it seems that if you go to the Code tab, it is enabled, but disabled on all other tabs.

KjellMorgenstern commented 2 years ago

We still observed it on 0.9.10 during testing. It seems only to happen on first start, when the config file needs to be created or migrated. So simply restarting could help. I didn't check in detail, since finally getting out 0.9.10 has priority.

makermelissa commented 2 years ago

Unfortunately it's still happening after restarting the app. All good though. My workaround was enough.

failiz commented 1 year ago

Does this still happen in 1.0.1? If so, the workaround should be stated in the known problems of the release.