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
panicked at 'invalid expression while evaluating' #2483
Comments
AFAICS it's the When lowering the binding for width: tree_Expression::BinaryExpression { lhs, rhs, op } => llr_Expression::BinaryExpression {
lhs: Box::new(lower_expression(lhs, ctx)),
rhs: Box::new(lower_expression(rhs, ctx)), <-- rhs is Expression::Invalid
op: *op,
}, |
The viewer and LSP don't lower to LLR, this is probably in the eval phase of the interpreter. But if the LLR makes invalid code, this probably fails for the same reason. |
Yes, the above is with slint-compiler, but with the interpreter it's exactly the same: Expression::BinaryExpression { lhs, rhs, op } => {
let lhs = eval_expression(&**lhs, local_context);
let rhs = eval_expression(&**rhs, local_context); <-- rhs is invalid |
The previous code was only re-creating the layout properties for these that had a binding, but that wasn't done if the property was just read, leading to access to non-existing properties later. Fixes #2483
The previous code was only re-creating the layout properties for these that had a binding, but that wasn't done if the property was just read, leading to access to non-existing properties later. Fixes #2483
The previous code was only re-creating the layout properties for these that had a binding, but that wasn't done if the property was just read, leading to access to non-existing properties later. Fixes #2483
This is with slint-viewer/slint-lsp 0.3.5, I tried it in the 1.0 SlintPad and it seems to panic there as well.
The text was updated successfully, but these errors were encountered: