Well, it appeared to be fixed when I upgraded from Mojave to Big Sur, but it’s all still a little unpredictable. I’m on 11.6 and the latest SU build and inexplicably it sometimes happens still. It works %99 of the time and the fault is so intermittent that for a while I thought I was crazy. But I finally caught a .gif of it happening, actually switching from not working to working mid operation.
Screen recording and screenshots are now build into macOS, you don’t need to use QuickTime Player. You can type command-shift-5 to bring up the recording options, and command-shift-5 when you’re ready to stop recording.
There are reasons some of us need to try and hang back no further than Mojave for as long as possible. I’m going to have to consider a dual boot setup with Mojave on one drive/partition and latter MacOS on the other.
Colin, were you able to identify what might have fixed the issue? I’ve had a quick look at a comparison between my original and the ‘new, clean’ version of this file, and can’t see any differences that look likely to affect the issue, with one possible exception:
I am on BigSur 11.6 and SU Pro 21.1.331. However I upgraded to BigSur in an unsuccessful attempt to resolve this issue, I first experienced the problem on Mojave.
Regenerating a new privatePreferences.json file fixed the issue for me as well. However that did cause me to lose all my other extension preferences.
I then restored my original privatePreferences.json file, and the problematic behavior returned. I then removed just the TPDT key/value pair in the original file, saved, and restarted Sketuchup. The the issue was again resolved. Adding the key/value pair back to the file reproduced the issue again, so at least for me that is definitely causing the problem.
I also noticed that when I regenerated the new JSON file that property was missing entirely, so for whatever reason it was not generated as part of the baseline configuration.
Specifically, this is what I removed from the JSON file:
Update: This fix is not permanent. After deleting the TPDT property, it gets regenerated and the column widths are again stuck. @colin any update internally on a permanent fix or what the TPDT JSON property actually does?