-
Notifications
You must be signed in to change notification settings - Fork 183
Description
Describe the bug 📝
Not sure if this wasn't included for a reason but i believe it's what's causing some bugs with my implementation of the LenghtMeasurer tool and a custom Exploder tool i have been building (will create a feature request as promised next week!).
Long story short, i need to determine whether the LenghtMeasurer tool has finished creating a measurement, or if it has only defined the starting point. In the the v2.0 of Open Engine, i could read the ._temp.isDragging value to achieve this. However, it seems that in the newer v3.0, this value isn't being updated in sync to the tool (when defining the start and end points using the left mouse click, the isDragging value is always false). I believe it's because the only place when the value seems to switch to true is within the initPreview() method, which is async. However, every time this method is called, there isn't a corresponding await, meaning it maybe could not trigger a timely update to the isDragging variable. I have left code screenshots below to show what i mean.
Like i said in the beginning, i don't know if this behaviour is intended (or if there is an easier way to determine if the LenghtMeasurer tool has finished the create measurement process), but i thought it could be useful to share this discovery here.
Reproduction ▶️
No response
Steps to reproduce 🔢
- Define start point of measurement with the LenghtMeasurer tool
- Check isDragging is false
- Define end point of measurement with the LenghtMeasurer tool
- Check isDragging is still false
System Info 💻
System:
OS: Linux 5.15 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
CPU: (8) x64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Memory: 7.46 GB / 15.59 GB
Container: Yes
Shell: 5.2.21 - /bin/bash
Binaries:
Node: 24.9.0 - /home/arocha/.nvm/versions/node/v24.9.0/bin/node
npm: 11.6.0 - /home/arocha/.nvm/versions/node/v24.9.0/bin/npmUsed Package Manager 📦
npm
Error Trace/Logs 📃
LenghtMeasurer create() method

LenghtMeasurer initPreview() method
Validations ✅
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
- Check that this is a concrete bug. For Q&A join our Community.
- The provided reproduction is a minimal reproducible example of the bug.