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

Keyboard stops working while typing #815

Open
SlimRunner opened this issue Feb 23, 2024 · 2 comments
Open

Keyboard stops working while typing #815

SlimRunner opened this issue Feb 23, 2024 · 2 comments

Comments

@SlimRunner
Copy link
Contributor

SlimRunner commented Feb 23, 2024

const monkeypatchedFunction = function (
...args: Parameters<Fn>
): ReturnType<Fn> {
const handlersArray = (obj[prop] as HookedFunction<Fn>).handlers;
for (const h of handlersArray) {
let stop = false;
let ret: ReturnType<Fn> | undefined;
h.fn((r: ReturnType<Fn>) => {
stop = true;
ret = r;
}, ...args);
if (stop) return ret as ReturnType<Fn>;
}
return oldfn(...args);
};

The error trace in Desmos points to this function. It happened under two different machines in Firefox (Windows) on the current Desmodder version available for Firefox. Also, yesterday it was in Calculator. Today it happened in Geometry.

I have not being able to reproduce reliably the bug, but basically as you are typing you just cannot type anymore in that specific expression that glitched out. The other day it happened multiple times, but I was in rush putting together a graph, so I simply duplicated the expression and deleted the one glitching out to get rid of the error.

The last thing I typed this time was this
image

I tried to retype this and it does not reproduce the error. What seems to trigger it is navigating and selecting things as you type. Also, one thing to point out is that sometimes you can type, but you cannot move. After this error during the same glitched session I disabled all the plugins and the error persisted.

Addendum: apparently it can lock the graph from being dragged as well.

@SlimRunner
Copy link
Contributor Author

My bad I forgot to put what the error was. It was too much recursion.

@ronwnor
Copy link
Contributor

ronwnor commented Feb 23, 2024

I get this fairly frequently too.
I'm able to consistently reproduce it by spamming 0s:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants