Search Type: Posts; User: akopov

Search: Search took 0.01 seconds.

  1. Solved it:

    1. Directly assigning new config to myGrid.propertyNames works actually works fine.
    2. This should be done BEFORE a new source is assigned - apparently setSource() redraws the grid...
  2. I'm trying to use my PropertyGrid component in Sencha Architect with different objects, so the set of properties it is supposed to display is not fixed.

    While I have no problems assigning new...
  3. Thanks again for your help, and sorry for some ranting above, I was just extremely frustrated. Now when I know what to look for when I happens again it doesn't look that critical.
  4. Thanks for your reply

    I'm only starting with the product so my code is probably not following best practices. Empty store is there to access it later in runtime and populate it dynamically. It'd...
  5. Sorry for spamming, but I have just open manually fixed project, saved it and closed.

    It won't open again this time, perhaps again self-inflicted damages, this is ridiculous :(
  6. Having "exportPath" property set to the path that doesn't exist seems also to crash SA on load.

    Makes sharing projects between different developers a bit tricky, still is a minor issue comparing...
  7. Found the problem!

    One of my stores I have converted from XML store into JSON store was still had {"type": "xmlstore"} in its metadata file while other properties were changed to JSON store one....
  8. Noticed a couple of irregularities in project files, e.g. xds profject file and Application and Explorer metadata files were listing 'Folder' model which was actually renamed to TreeNode (for some...
  9. Sencha Architect won't open the project I have successfully working on yesterday. Until I closed SA everything was fine - no errors neither in SA nor in deployed JS generated. Then when I reopened...
Results 1 to 9 of 9