Search Type: Posts; User: Stuart-SwarmOnline

Page 1 of 5 1 2 3 4

Search: Search took 0.04 seconds.

  1. You should use the Form's setValues or setRecord methods and it will match the data properties to the appropriate form fields based on their names.
    ...
  2. If you add the view as you would any other class, include the package in your main app and then reference the view with its class name or alias then it should work as normal.
  3. i think you will have to define the association the other way too, i.e. add a reference from the Person model to the Address.
  4. A simple solution would be:




    store1.filterBy(function(rec){ ... });

    store1.each(function(rec){
    store2.add({
    id: rec.get('id'),
  5. That looks like a nice simple way of doing it. As you say, you will need to be careful with destroying the created components on each refresh to avoid a memory leak.Personally I probably would have...
  6. I threw together a quick demo which might be of use to you to get you started. It basically just matches "@Names" and displays them in a filtered dataview where you can select the one you want.
    ...
  7. That does seem strange. Could it be caused by conflicting IDs?Are the IDs and 'renderTo' part required? I would advise against using those if you can avoid it.
  8. I have tried this and the 'el' property contains the usual info that I'd expect.

    I created a <div> element with an ID of "Panel" and then ran your code in the console.

    50361
  9. This has come up a lot of the years and it was implemented in Sencha Touch but as far as I'm aware it hasn't made it into Ext JS.

    It wouldn't be too difficult to roll a quick version of your own...
  10. You might have to be explicit with your "requires" in the viewport and include all the parts to equate to the path. I've found that I had to do this and haven't found the "right" way to do it yet. So...
  11. Sorry, I'm not sure what you mean.
  12. Instead of setting the Loader Path try adding the package to the app.json file in the requires option.



    "requires": [
    "App1Package"
    ],
  13. What errors are you getting? How are including the new package in your main app? Are you able to make a test case available so we can see exactly what's happening?
  14. If the package is included correctly you should be able to reference views by their name/alias as you normally would but they'll likely be in a different namespace. For example, in your MyApp...
  15. It can definitely be done and packages can contain their own MVC structure. I think the difficulties come when requiring the necessary files and ensuring all controllers etc are initialised. If you...
  16. You can use the 'cellcontextmenu' event and interrogate the data of the record targeted and customise the context menu displayed based on that. Something along the lines of:





    ...
  17. I think you will have to serialise your data object into a JSON string and have your serverside automatically decode that into your serverside model. I believe you can do this with ASP.NET MVC but...
  18. I would take a look at Packages (http://docs.sencha.com/cmd/5.x/cmd_packages/cmd_creating_packages.html) which should allow you develop different areas in isolation and then pull in each part to your...
  19. You should be able to call Ext.define when you have the details of your new model's fields and create it then. This is a useful article that goes into this problem...
  20. Some more details and a code snippet would help us come up with some suggestions as to why this is happening.
  21. If you know the ID of the Order item then you should be able to locate it within the Orders store and add the newly loaded record to the Items associated store. If the Item record has an ID then it...
  22. You will need to override the 'set' method of the Model class which determines whether a field should become dirty or not.

    Perhaps you could wrap the following snippet (taken from the 'set'...
  23. You're welcome - glad it's now working!
  24. As a trivial example that you can run in Developer Tools inside the Ext JS Docs this snippet returns the raw data, unchanged even after the 'set' call.



    window.rec =...
  25. The 'raw' property should just contain the raw object that was used to create the record in the first place so can just be interrogated as a normal object with the dot-notation, using the field names...
Results 1 to 25 of 120
Page 1 of 5 1 2 3 4