Area measurement has a slow click

When I use the area measurement function in the official 7.1 version demo, the click response speed is relatively slow, which is different from the previous version.
This is the current version of 2024.7.1.
6

This is an earlier version from 2022.
8

It can be clearly seen that earlier versions had a faster click response speed when measuring area. The same problem also exists in line segment measurement.The 2024.7.1 version is relatively slow, can the effect of the new version be optimized?

Thanks.

Hello @619944680,

Just a few questions:

  1. Is the area operator you mentioned your custom operator?
  2. Are you getting any messages in the browser dev console when making the measurement?
  3. The GIFs you uploaded are for two different models. When using the same models, is the slowdown still there?

I’ve tested a line measurement and the performance looks to be identical.

Thanks,
Tino

Hello,Tino,

This operation was not customized by me.I assign the viewer object after the model is successfully rendered to the window object in the 2024 and 2022 files respectively, and then call the viewer.operatorManager.set (Communicator. OperatorId. MeasurePointPointDistance, 1) on the browser dev console to activate the operation of measuring surface products or measuring line segments.

I did not getting any messages in the browser dev console when making the measurement.

I used the same model to re measure in different versions, and this is the performance of the 2024 version:
2024

And this is the performance of the 2022 version:
2022

It can be seen that the click response speed is not very fast when measured in the 2024 version. But the 2022 version is smooth.

Thanks.

Hello @619944680,

Thanks for providing the additional information.

The default point-to-point measurement operator only measures the distance between two points. Could you provide more details on how to reproduce the behavior of your operator on my end? Feel free to send me a direct message if that is more your preference.

As as aside, with the release of HC 2024.6.0, a single Web Viewer can support multiple views. But it’s not clear if this is indeed having an effect on the performance of your operator.

Thanks,
Tino

Hello,Tino,

Thank you for always following up.

Firstly, I assign the viewer object in Toolbar.js to a custom window.viewer object:

Then execute function OperatorManager.set in the browser dev console.
Here, the OperatorId parameters are set to 23 and 24 respectively, representing MeasurePolylineDistance and MeasurePolygonArea.
2022

You can see that there are two issues:
1.When measuring the area, only three points can be clicked, and the fourth point cannot be clicked, which results in only measuring the area enclosed by three points. In previous versions, multiple points could be clicked continuously and the area of irregular areas could be measured;

2.Whether measuring area or measuring line segments, the display results are relatively slow when clicking to calculate data.Usually occurs after the second click.

I don’t know if my description is clear, if there are any doubts,feel free to send me a direct message.

Thanks.

Hello @619944680,

I was focused on the operators available in the default UI. Indeed, Communicator does have MeasurePolygonArea and MeasurePolylineDistance but those are not included in the default UI.

At any rate, I can reproduce the issue in my testing. I’ll go ahead and create an support ticket for it.

Thanks,
Tino

1 Like

This feature is very important for my project development.
Thank,Tino. :grinning:

1 Like