So, I've been working on binding components to each other so they can all move based on one singular component. After I've saved the view, once it's closed and reopened, my binded components have scattered and I have to reset the binding.
Image 1: what it's supposed to look like on the x and y positions for the component.
Image 2: after reopening the view notice how the x and y say "null" rather than the binded position as in image 1.
I don't know why this is happening, if someone can help explain it/how to fix it because it's happening on other views as well.
Can you show us the binding configuration? The binding is returning null so the problem is with the binding.
This is for the x position but the y position is the exact same +CL1-01.width +3
I would expect that to work more reliably if you used a Property binding then added the offset with an expression after that.
I don't know if the expression binding is being triggered after the parent value changes or if it runs once on startup of the window then never again.
That's what's weird is that the 4 views before that doesn't have this issue and they have way more components
Show the binding that is null, then look at the the expression and see what the error is.
Whenever I open the binding, the "preview" gives the proper number there is no real error
Are you sure you don't have a circular reference somewhere?
To @Transistor point, there is something else going on, maybe uncheck persistent for those two props, save and close the view and open back up.
Edit, also, if you hover over the red triangle it will give you more about the errors, but the errors are probably just that the prop is getting a null.
This would be typical behaviour if the binding does not update after the page loads. the binding update is prompted by opening the configuration window.
I unchecked persistent and the same problem occurred. And the errors on the triangle are just errors about it being "null"
There is not a circular reference. The expressions are all modelled after the same simple expressions.
So it seems if I remove the binding that pulls the actual name of the component and save it works? I have no idea why that would be causing an issue but it's a current solution.
Can you explain what this means?
1 Like
