Harald Steinlechner

see 58f1d14ab0a8450cc71ca1375db1fcd586cee7cc (https://github.com/pro3d-space/PRo3D/commits/bugs/triangleFilter/)

please refer to advanced annotations docs. The relevant part is currently stored here: https://github.com/pro3d-space/PRo3D/pull/542/commits/54ff51f2545b7727b8bd2121a94a3a90a5d35c83#diff-5b8179e37acaceeb2a6bf8b9ce4ceedf9785501303594064bbee53391179b622R88 Cursor size, and enabled state should be serialized to the scene (i think scene config or...

In another project where i have realtime picking preview (which would be absolute boost in pro3d also) i have hot keys for chosing "the second" pick. This only makes sense...

``` adaptive { match! currentSelection with | Surface -> yield! surfaceUI | Annotation -> yield! annotationUI } ``` something like that?

well i think the decision (here a union) could be a more complex context aware condition computed from the relevant parts of the model. The only disadvantage is that larger...

what would be the most important single property tab aspect? what could we use to test it out? Just a properties tab wich either surface or annotation properties inside, right?...

i got rid of multi-objs merging multiple query results into a single one (quick & dirty, mind the default color which needs to be provided: https://github.com/pro3d-space/PRo3D/commit/5367721028c10fb9f10dcb85e3cb0a93fef560e9#diff-e8c377dfd6a4113e3c919a1e2a192fe7a47476105ecd46a4f1f1a69cbf1a6b29R15) what puzzles me is...