Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format
Sencha Premium User
Editing component properties as object causes crash
Architect Build tested:
- When I try to edit a property as an object in the project inspector's configs, in this case "root" on a treestore and "layout" on a panel, Architect quits with a runtime error. This happens both on a Windows and a Mac machine. It crashes after I enter a few lines or even characters, either when clicking "save" or spontaneously.
- For now, how could I fix this manually? Writing directly to metadata?
- UPDATE: Adding a proxy to the treestore before editing the root object seems to fix at least the crash on the root object.
Steps to reproduce the problem:
Okay so you add a TreeStore and then go to he root configuration and put
in and it crashes? Can't reproduce it here
Any additional steps or a video may help us.
Sencha Premium User
I was able to reconstruct both issues:
1. In the attached sample, if the tree store does not have a proxy defined, almost any input to the tree store causes a crash, such as changing the class name. It's not just the root property. With the memory proxy, it works fine. I remember reading that a memory proxy is default, so I assumed I don't have to specify it.
2. If I add a panel to the views in the attached project and edit the layout object, it crashes while typing. The error message says: "TypeError: 'undefined' is not an object (evaluating 'layoutDefinition.layoutConfigs')"
That happened on different machines (mac and win). One issue might be that I have the development folder in dropbox. But when reconstructing it, it even happens outside of the dropbox.
Looking into this now, get back to you soon
I can get this to crash on number 2 using build 676 (latest production). In the next release you will no longer be able to convert layout to an object. Layout is fairly special and should have never been given a multi-type.
Number 1 however I could not get to occur. Editing the userClassName and the root property did not provide errors or anything unexpected.