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

Rework Evok initialization #164

Open
kratochvil01 opened this issue Jun 18, 2024 · 0 comments · May be fixed by #193
Open

Rework Evok initialization #164

kratochvil01 opened this issue Jun 18, 2024 · 0 comments · May be fixed by #193
Assignees
Labels
enhancement New feature or request

Comments

@kratochvil01
Copy link
Contributor

The current initialization of Evok is synchronous and the steps for switching to asynchronous mode have been performed recently. This solution is of historical origin.

It is necessary to modify the initialization cycle of the Evok so that it runs asynchronously from the beginning and does not create potential problems with the creation of asynchronous objects.

For some devices it will be necessary to force the sequence.

@kratochvil01 kratochvil01 self-assigned this Jun 18, 2024
@cleveHEX cleveHEX added the enhancement New feature or request label Jun 19, 2024
@kratochvil01 kratochvil01 linked a pull request Oct 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants