-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Marker flashed in the wrong position #369
Comments
#370 was assuming problem is caused by the display timing. But the marker is created with same params, it should has the right position in the first place. I can force visible to false on create and set default value for visiable, so |
@martesi Can rolling back the code fix this issue? I always believed there was nothing wrong with the previous one. |
You mean v7.0.1? I have pinned the version to v7.0.0 so far. v7.0.1 works fine without strict mode, but I personally like to keep it open, as the reason react recommended it. If that's decided, I can opt out strict mode and provide feedback based on that. |
This is actually my own fault. As mentioned earlier, the initial props are passed to Marker constructor on create. In this scenario, Marker should be placed at the right position in the first place. In this case however, I used a signal that will trigger a effect to update position state. Instead of relying on the position state, I used the signal to control Marker rendering. So the marker is rendered with position I suppose the old implementation of Thank you @jaywcjlove for patient replies and quick responses. Since the new implementation is now not involved with BTW, |
|
Marker
andText
are showed byuseVisible
before their positions are set to the correct ones byuseSettingProperties
.In v7.0.2, this causes flashes.
The text was updated successfully, but these errors were encountered: