Skip to content
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

Closed
jarodise opened this issue Feb 18, 2022 · 12 comments · Fixed by #6866
Closed

Cursor-trace offset when drawing in Excalidraw #4270

jarodise opened this issue Feb 18, 2022 · 12 comments · Fixed by #6866
Labels
dependencies Pull requests that update a dependency file draw Excalidraw :type/bug Something isn't working. Affects daily use. upstream Blocked by upstream deps

Comments

@jarodise
Copy link

jarodise commented Feb 18, 2022

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

CleanShot 2022-02-18 at 19 56 38

Desktop Platform Information

MacOS Desktop version 0.6.0

Mobile Platform Information

No response

Additional Context

No response

@andelf andelf added :type/bug Something isn't working. Affects daily use. draw Excalidraw upstream Blocked by upstream deps labels Feb 18, 2022
@andelf
Copy link
Collaborator

andelf commented Feb 18, 2022

Many thanks.

This is a upstream bug in checking scrollable parent element.

excalidraw/excalidraw#4806

@andelf
Copy link
Collaborator

andelf commented Feb 19, 2022

This will be fixed when upstream Excalidraw has a new release.

See-also: #3414 #2870

@andelf andelf added the dependencies Pull requests that update a dependency file label Feb 19, 2022
@mrmign
Copy link

mrmign commented Mar 3, 2022

I open the .excalidraw file in vscode with excalidraw plugin installed, it works well.
so i think the upstream Excalidraw should have already fixed the bug.

@lynzrand
Copy link

Seems like the upstream patch has already been merged, are we able to move forward on this issue?

@filipenko4791
Copy link

Still having this issue with version 0.7.1 (same specs as mentioned above). Is there any fix?

@lihaokx
Copy link

lihaokx commented Jun 11, 2022

@filipenko4791
YEs. I have the smae issue.

@constfold
Copy link

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

@jjloder
Copy link

jjloder commented Sep 10, 2022

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?

@jjloder
Copy link

jjloder commented Sep 10, 2022

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.

@falsethesis
Copy link

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

@alxlg
Copy link
Collaborator

alxlg commented Sep 20, 2022

@andelf Excalidraw seems to have released version 0.12.0 while Logseq still uses 0.10.0, can the dependency be updated now?

@JasonPekos
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file draw Excalidraw :type/bug Something isn't working. Affects daily use. upstream Blocked by upstream deps
Projects
None yet
Development

Successfully merging a pull request may close this issue.