Description 📝
Hi there!
It would be nice if we could instruct items to stay visible but not clickable, so that we can still select what’s behind/inside them.
An example use case is visualizing IfcSpaces transparently, while still being able to select items inside or behind the IfcSpace (e.g. a floor or installation).
I tried excluding via highlighter.selectable; it does stop them being selected but it doesn’t allow clicking behind the element.
I suppose the crux is that picking goes through the GPU (not real raycast), so there's only ever the frontmost item to work with.
Suggested solution 💡
- Ability to use raycasting for clicking, preferably with a list of items instead of the foremost one (*).
- Ability to have an element as non-selectable:
- can be some kind of boolean or set
- or via a lambda whether item must be included
- or manually filtering the list of items, see (*)
Making it configurable can make sense, as it may impact performance.
Alternative ⛕
No response
Additional context ☝️
No response
Validations ✅
Description 📝
Hi there!
It would be nice if we could instruct items to stay visible but not clickable, so that we can still select what’s behind/inside them.
An example use case is visualizing IfcSpaces transparently, while still being able to select items inside or behind the IfcSpace (e.g. a floor or installation).
I tried excluding via
highlighter.selectable; it does stop them being selected but it doesn’t allow clicking behind the element.I suppose the crux is that picking goes through the GPU (not real raycast), so there's only ever the frontmost item to work with.
Suggested solution 💡
Making it configurable can make sense, as it may impact performance.
Alternative ⛕
No response
Additional context ☝️
No response
Validations ✅