2024-04-12 01:44 AM
The Shift and Option keys are inconsistent and sometimes non-operable when working in a Design Option plan.
Operating system used: Mac Intel-based Ventura 13.6.3
Solved! Go to Solution.
2024-04-13 01:39 AM
Unfortunately the problem occurs when the focus is in any palette or input field (on Mac this is indicated with a blue highlight). The modifier keys aren’t correctly recognise when trying to interact with the model view directly - once the focus from these locations goes back to the model view then the modifier keys behave as expected.
However, we have managed to find a solution to this and it will be fixed in the next main release coming later this year.
2024-04-12 03:11 AM
I don't understand why that would be the case.
An element in a design option is no different to an element in the main model.
It just happens to be tagged with a design option that allows it to be turned on or off - similar to layers.
It should not affect how the element is edited or placed.
Exactly what problem are you having?
For example - you can't use SHIFT to constrain horizontally when placing a wall with a design option, but you can in the main model?
Barry.
2024-04-12 08:11 AM
This issue with sticking and non-responsive modifier keys (shift, opt etc) seems to occur as soon as you interact with the Design Options Palette. If you touch anything within the DO palette and then try to initiate a modifier key operation in the floor plan window the modifier key seems to stick. If you hit escape multiple times it clears and works as normal. Everything is then ok until you interact with the design options palette again. I’ve reported this to support.
2024-04-13 01:39 AM
Unfortunately the problem occurs when the focus is in any palette or input field (on Mac this is indicated with a blue highlight). The modifier keys aren’t correctly recognise when trying to interact with the model view directly - once the focus from these locations goes back to the model view then the modifier keys behave as expected.
However, we have managed to find a solution to this and it will be fixed in the next main release coming later this year.