It would be nice if IfcAnnotation was easier to select.
A lot of times, when you're in drawings, and trying to select an IfcAnnotation, it selects the objects behind the annotation. A lot of times, you have to alt+click
to see a menu of overlapping things--and then select the annotation.
To speed up the process, I wonder if there was a way to 'bias' IfcAnnotation so it was easier to select the first time.
AI braindump...
https://chatgpt.com/share/6824f281-90cc-8013-8d89-b41a914aa8a6
Comments
One could ask whether in "Drawing mode" you should be selecting/editing the underlying elements at all!
oh man, that's crazy talk. ;) I model in drawing mode all the time.
Might be nice as an enhancement though. Maybe an option to disable selection of non-annotation related elements, while still allowing snapping. Would make editing annotations a smoother experience.
As far as I know the selection order when several objects overlap is driven by the order in which they were created. Maybe that might help, although I think any solution using this as a workaround will be inherently hacky. I think it would be better to make some objects dynamically unselectable depending on the context.
@Gorgious what's your thoughts about using Raycast--something like the following AI suggestion?
https://chatgpt.com/share/6824f281-90cc-8013-8d89-b41a914aa8a6
Hehe looks like a good idea but I don't think it actually is... I think it's a bit overkill, I'd rather add a button in the interface to toggle selectability of every non annotation object than using a modal operator for it. Besides raycast only works with polygons Afaik so it would rather need to be a kdtree implementation. Also I would be cautious with overriding common features such as left click, bonsai already does a lot of this and these functions are usually several hundred lines of code because of all the edge cases. And what about the fact that constantly running modal operators disables autosave 😅 Cheers