Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Local transformations & new LoD Metric #495

Open
wants to merge 17 commits into
base: develop
Choose a base branch
from

Conversation

LauraFritz14
Copy link
Collaborator

recomendet workflow:

  • select surface
  • enable "use Pivot", "show PivotPoint" and "show local RefSys" via Transformation gui
  • select "PickPivotPoint" or "PickSurfaceRefSys" in the picking interactions dropdown to pick pivot and local reference system
  • do the local transformations via Transformation gui

Note: this approach is only useful for small translations. big translations and a new position of the local reference system effect a relocation of the surface.

haraldsteinlechner and others added 17 commits December 17, 2024 17:38
…phic annotation performance (in e.g. shaler) [(String.IsNullOrEmpty text) || (show && visible)] #481
… for large models due to per-value field containing the whole drawing state)
… loading the lowest quality kdtree unfortunately is too expensive, so i teaked the old legacy metric
…iate frames instead of classic scalbars (renamed ScaleBar to ScaleVisualization to reflect his additional visualization behavior), Outline rendering: optional parameter for thickness
@haraldsteinlechner haraldsteinlechner changed the base branch from main to develop February 17, 2025 08:27
@haraldsteinlechner haraldsteinlechner changed the title Local transformations Local transformations & new LoD Metric Feb 17, 2025
Copy link
Collaborator

@haraldsteinlechner haraldsteinlechner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to avoid confusions, i suggest we do some simple UI hints / tooltips etc in addition to a markdown documentation in /docs explaining the more complex bits of the transformations

@@ -689,15 +689,15 @@ module ScaleBarsApp =
let inRefFrame =
refSys.Current
|> AVal.map (fun refSys ->
TransformationApp.getReferenceSystemBasis V3d.Zero refSys
TransformationApp.getReferenceSystemBasis_global refSys //TODO: local or global?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this could be controllable in scalebar settings. Since this could be a source of confusion i suggest adding at least a note in the UI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants