You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's very frustrating when the cursor can not keep up. There is a 5 second delay when I press the backspace to correct something. When I correct it, I have to wait another 2 or 3 seconds to see if the cursor is in the correct position before I start typing again.
There are known issues with rendering performance on certain Linux environments (#587), however there are no known issues with Windows, and we cannot reproduce this issue on any on our internal Windows devices
I have some additional questions
Are you editing a regular query or a file?
Does the rest of the UI suffer from performance issues, or just the query editor?
Have you tried clearing your query history?
Does this affect both the web app and desktop app?
UPDATE:
I switched my desktop environment to Fedora 41 (Not because of this problem, but microsoft is getting creepy)
I'm not having any issues with the .rpm and Fedora 41.
Describe the bug
It's very frustrating when the cursor can not keep up. There is a 5 second delay when I press the backspace to correct something. When I correct it, I have to wait another 2 or 3 seconds to see if the cursor is in the correct position before I start typing again.
Steps to reproduce
Just use it on Windows 11 Pro
Expected behaviour
Should be fast, no delay.
Surrealist Environment
Version: 3.1.9
Flags: feature_flags: false, query_view: true, explorer_view: true, graphql_view: true, designer_view: true, auth_view: true, functions_view: true, models_view: true, sidekick_view: true, apidocs_view: true, themes: true, syntax_themes: false, newsfeed: true, database_version_check: true, highlight_tool: false, legacy_serve: false, cloud_enabled: true, cloud_endpoints: production, cloud_access: true, cloud_killswitch: true, changelog: auto
Contact Details
[email protected]
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: