We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem
When running a Desktop app on Windows 10, updating RSX quickly after it was rendered causes an error in the console.
Steps To Reproduce
Run this component on the Dioxus Desktop platform in a Windows environment.
fn app() -> Element { let mut data = use_signal(|| false); if data() { println!("RAN1"); rsx!("true") } else { println!("RAN2"); data.set(true); rsx!("false") } }
Expected behavior
true should be displayed instead of false and there should be no errors.
true
false
Screenshots
This error is shown in the console when the true branch of the if statement is run.
Environment:
main
0.5
1.77.1
Windows 10
Desktop
The text was updated successfully, but these errors were encountered:
This also happens with if, else if and else statements inside of RSX blocks:
if
else if
else
fn app() -> Element { let mut data = use_signal(|| false); rsx! { if data() { "true" } else { {data.set(true)} "false" } } }
Also happens on release.
Scratch this. It's not based on conditionals but rather seems based around how quickly a signal or hook is updated.
Sorry, something went wrong.
ealmloff
Successfully merging a pull request may close this issue.
Problem
When running a Desktop app on Windows 10, updating RSX quickly after it was rendered causes an error in the console.
Steps To Reproduce
Run this component on the Dioxus Desktop platform in a Windows environment.
Expected behavior
true
should be displayed instead offalse
and there should be no errors.Screenshots
This error is shown in the console when the
true
branch of the if statement is run.Environment:
main
,0.5
1.77.1
Windows 10
Desktop
The text was updated successfully, but these errors were encountered: