We've prepared a beta of an update that should resolve the issue with Emojis and Dictation interfering with using the 'e' and 'd' keys.
Download whatever is the latest Mac beta (1.60.15 at the time of writing);
This is a rushed beta and could contain other regressions, since the development Mac didn't survive the Monterey upgrade, so this is a new build system on an M1 Mac.
One regression we're investigating is the "webview" crashing on M1 Macs. A webview is used to show e.g. the Error Log in the About menu. We would like feedback on the systems this is crashing on, and are interested in finding out whether the crash is tied to M1 (ARM chips), or Mac OS Monterey (on ARM or Intel chips). Please drop notes with your system configuration if this function crashes for you.
Have you installed the latest version from the website? It has been out for some time.
I've tried this solution but I'm still having the emoji issue. Please dvise
Me too issue. When trying to label with the annotation option and typing "D","E", or "F" when editing a label For "D", it defaults to trying to use the dictation option in the edit menu. For "E", it defaults to trying to use emojis
For "F", it defaults to full screen
wich are supposed to be shortcuts when holding the "fn" key on my Mac. It's running as if the "fn" or function key is always being pressed. Its definitely not and definitely only happens when using Shot Designer. I've updated my keyboard settings to try and modify the short cuts but still doesn't work or change the function within Shot Designer. Really looking forward to the update. For now my only workaround is to type my annotations in a separate app, copy and paste into the annotation box. •Using 2019 MacBook Pro 16" / Monterey 12.1 •Using Shot Designer Pro which I've paid for and is up to date to my knowledge (clicked on "check for update" with no progress or message saying anything).
Another "me too" post, but seeing this behavior with importing images to cameras. I can import one image without issues. If I import a second, the app freezes on the import dialogue box, and the only fix is to force quit and come back in (fortunately, nothing is lost, but still a nuisance). Monterey with the beta build 1.60.15. Thanks.
It has been reported by about 10 people now. Still doesn't happen here. I've collected system reports from most affected people, and trying to find the common denominator.
Jcdelpias, is the problem still happening with multiple props? You seem to be the only one it's happening for, and it makes my brain cross-eyed. I saw the video, no doubt it's happening.
The beta fixes the issue with e (and d) on 12.1 running on a Macbook Pro 15" 2016 model. No problem here with multiple props.
Unfortunately my other laptop doesn't support Monterey, and I didn't find any other solution than to quit and relaunch SD after having imported one pic...
I'll check on Saturday, though I'm note quiet certain my older computer can run OS12... I'll let you know.
Sure, but i'm interested in whether you also see this on a 12.0 computer, and then if it breaks when you update that computer to 12.1.
Actually I have updated to MacOS 12.1 (build 21C52), officially released three days ago.
You're apparently the only one, but you're also running a beta version of the next Mac OS. If you have other Macs, does it happen on the Macs that run 12.0? And if you're willing to upgrade one of these other Macs to the 12.1 Mac OS beta, does it then stop working? I'd love to understand if this is tied to the next Mac version. I can't risk upgrading the build machine unless it's the only way to address it.
Hi Per, though having updated to 12.1 official release, I still get this weird app freeze when importing a second image... Does anyone here encounter that bug ?
Which are the other problems? The purpose of the beta is to found out if there are other problems before releasing to a wider audience.
the "e" workaround works great , the "d" workaround does not. BUT a Capital "D" will work . This is not using the "Beta" release which seemed to have other problems. I've returned to the earlier version 1.60.12 for now
Communicated via email, still unable to reproduce it. If others also have this issue, please post here.