We value your input! Please participate in Archicad 28 Home Screen and Tooltips/Quick Tutorials survey
2024-03-07 05:00 PM
Has anybody noticed this also and found a way to make this behaviour go away?
I select any element (either on plan or 3D view) and if I don't wait for 1-2 seconds after selecting the item, the element will always think I want to move it. Therefore, if I am trying to work quickly and just select the item and then move the mouse over the the Info Box to edit any settings, the settings will be grayed out because the element is in the middle of a move command !
I've been using Archicad since version 10 and this has now been happening on version 26 and 27, but only if I use any of my Apple M1-equipped Macs. I use a MacBook Pro and a Mac Studio, both of them with the Apple M1 Max chip and they both behave the same.
Does anyone think of any possible setting in the Work Environment that could help with eliminating this behaviour? It gets kind of tiring trying to quickly select items, but having to wait a couple seconds after selecting a wall, a slab, an object, etc., because if I don't wait then it'll think I want to move the objects.
Solved! Go to Solution.
Monday
For me Magnet was the culprit (window manager): https://magnet.crowdcafe.com
I need to quit Magnet when working with Archicad, then I can normally work again.
2024-03-08 01:56 AM
That is strange and you have tried two different Mac devices and you are still getting the same problem. When troubleshooting were you using the same mouse on both devices when testing ? Keep trying different things and make sure your mouse is fully charged.
2024-03-08 02:31 AM - edited 2024-03-08 02:36 AM
I have this problem too since the release of AC26. Finally someone asks. Thanks.
I’m using M1 MacBook Pro and AC26. I think this is an obvious bug.
It happens even when I don’t connect my mouse, just using the built-in trackpad.
I can’t find any way to work around this bug.
2024-03-08 05:37 AM
M1 Max MBP here, same behaviour - really annoying.
2024-03-08 06:58 AM
The mouse is not the problem. It happens independently if I use:
I just got my new Apple M3 Max unit today, in the process of installing everything, so I'll report in the event this does not happen with the M3 Max chip and is something only related to M1 Max.
2024-03-08 07:04 AM - edited 2024-03-08 08:18 AM
I am not having this problem. My M1 Mac was purchased in Australia at the end of 2022, I haven’t upgraded to Sonoma yet either. Would be good to hear if the M3 is any different ?
2024-03-08 07:15 AM
Is there any delay between when you select an entity and it highlighting?
AC22-23 AUS 7000 | Help Those Help You - Add a Signature |
Self-taught, bend it till it breaks | Creating a Thread |
Win11 | i9 10850K | 64GB | RX6600 | Win10 | R5 2600 | 16GB | GTX1660 |
2024-03-08 07:35 AM
@Roderick Anderson wrote:The mouse is not the problem. It happens independently if I use:
- The Apple Magic Mouse
- Logitech MX Master 3S mouse
- Logitech MX Anywhere 3S mouse
- The MacBook's trackpad
i use Logitech MX master & MBP trackpad. Same buggy behaviour
2024-03-11 03:38 AM
You could say there is a slight reply. When you select an element it kind of flashes a couple of times and after this it is selected. If you move the mouse (even if ever so slightly) during this flashing of the selection then it thinks you want to move (drag) the element.
I was paying closer attention to this on Friday, and it seems to me the behaviour does not happen all the time. I opened up AC27 and started working on a project and noticed "hey the problem is not happening" and then after a while it started happening, and then from that point forward it kept on happening. So it seems there is an action at some point that does trigger the behaviour.
I have completed setting up my M3 Max unit and will start working on a project on it tomorrow, so I'll report back if this also happens with that processor.
2024-03-12 07:06 AM
Just found, same behavior even when I only use remote desktop (Jump desktop) to control my computer and archicad. It’s obviously not related to any physical input device.
How can we raise this as a bug to GRAPHISOFT?