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
Cursor-trace offset when drawing in Excalidraw #4270
Comments
Many thanks. This is a upstream bug in checking scrollable parent element. |
I open the .excalidraw file in vscode with excalidraw plugin installed, it works well. |
Seems like the upstream patch has already been merged, are we able to move forward on this issue? |
Still having this issue with version 0.7.1 (same specs as mentioned above). Is there any fix? |
@filipenko4791 |
Any update on this? The upstream issue should be fixed in excalidraw 0.12.0. And I still encountered the same on 0.7.6 |
I've had this isssue for as long as I've used logseq, on both my old PC and my new mac. Fix or workaround? |
Huh, just toggled wide mode a few times and its now working normally. How odd. |
Toggling the view mode will fix the issue only temporarily. If you try to scroll through the page and write or move Items on the canvas after a toggle of the view mode the cursor will offset again. The issue still persists - Version 0.8.7 |
@andelf Excalidraw seems to have released version 0.12.0 while Logseq still uses 0.10.0, can the dependency be updated now? |
agree that this is very frustrating ... I found that clicking on the bullet containing the drawing instead of trying to edit it in the full page fixes the cursor offset, as a temporary workaround. |
What happened?
There is a big offset between the mouse cursor and the drawing trace when drawing with Excalidraw. the trace would show up 2-3 centimeter above the mouse cursor no matter what drawing tool you use.
Reproduce the Bug
try to draw something.
Expected Behavior
No response
Screenshots
Desktop Platform Information
MacOS Desktop version 0.6.0
Mobile Platform Information
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: