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

The ui is delayed after triggering a keybind #3

Open
caycun opened this issue Sep 6, 2024 · 1 comment
Open

The ui is delayed after triggering a keybind #3

caycun opened this issue Sep 6, 2024 · 1 comment

Comments

@caycun
Copy link
Owner

caycun commented Sep 6, 2024

After triggering a keybind, for example f + 2 it should select the second box immediately. But there is a delay, it only selects it once a new item has been read. Same with other events such as selecting and entering a box.

@caycun
Copy link
Owner Author

caycun commented Sep 6, 2024

The delay was slightly reduced by moving running variable to the top. But it's still not smooth because of the slight delay

Before:

while running {
       // do things here first before reassigning the value 
        running = handle_events(&mut app).unwrap();
}

After:

while running {
        running = handle_events(&mut app).unwrap();
       // do things here after reassigning the value
}

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

1 participant