Maybe a minor bug: working in form editor copying element

After copying an element say a textbox I can not change the name of the textbox (will not be saved). Refresh the browser.tab and it works again (unfortunately lost all open tab) Would be could, if open tabs are still there after refresh.

2 Likes

Iā€™ve been seeing a bug in changing bindings, I think is similar. Almost anytime I change a bind, I need to also change another property to make the IDE save. If I donā€™t, when I close the properties sidesheet and reopen, the bind will be reset.

Sometimes thereā€™s also another bug that prevents from typing in any properties field. This is usually due to an error in some field. I usually reset the state by saving a bind to any field and then removing it. It usually refreshes the state and allows typing again.

1 Like

Same issue with changing bindings. Refreshing usually fixes the issue too.

Any idea on how to replicate the issue?

Itā€™s inconsistentā€¦

Right now I just tried to see if I got the bug and it did, but itā€™s not doing anymore.

I just put a TextBox, clicked in the bind for ā€œplaceholderā€, typed self.item[ā€˜Testā€™] and pressed enter. No error. Clicked out of the component and opened the properties panel again and sure enough it didnā€™t stick. If I wait a few seconds, though, click away and click again, now itā€™s there. So maybe itā€™s just an interface delay?

1 Like

I wasnā€™t able to reproduce the copy renaming bug, or the failed to save data bindings. But weā€™ve identified the data bindings bug that causes property editors to become unresponsive, and weā€™ll update you when the fix is deployed.

For now, if you train yourself to hit Enter after editing a data binding, you shouldā€™t see the issue.

If you find the property editors become unresponsive, then going back into the data binding editor and hitting enter, should kick the IDE into working again. Otherwise refreshing the page will also work.

Edit: should now be fixed

4 Likes