Harald Steinlechner

Related, partly subsumed: https://github.com/pro3d-space/PRo3D/issues/192 and https://github.com/pro3d-space/PRo3D/issues/137 My proposal is to upgrade to the new orbit controller - to get rid of deprecation, smoother animation, less threads and maintained pointer apture...

Hi, thanks for the detailled descriptions. This all boils down to unconsistencies when scanning OPCs. It is concerned with "patches" vs "Patches" in the file system. I've tried to fix...

@LauraFritz14 is there some code duplication which could be resolved easily?

Try once more to reproduce and clarify with Rob if necessary.

actually i just figured out that it was already noted in the readme but totally forgot about it. I will merge develop to main to make this more apparent on...

after discussing this a bit again: one viable approach would be to add an additional "name" for surfaces like Human Readable Name, or "Nickname". would be quite small change.

Maybe via https://github.com/sshnet/SSH.NET? with file system virtualization not that hard, but it would require caching...

allowing grouping for scale bars is related to many grouping issues, e.g. https://github.com/pro3d-space/PRo3D/issues/312

This issue has quite some history. @gpaar What are the exact use-cases?

@gpaar can we get an example panorama for some known location to use it for testing?