Search Type: Posts; User: Animal

Page 1 of 5 1 2 3 4

Search: Search took 0.37 seconds; generated 42 minute(s) ago.

  1. This is not a dupe.

    This is all connected with the newly accessible ExtJS 5, and using a grid (or any other type of thing) as a picker (which you should be able to do!)

    A grid (or the other...
  2. I think it's suspending all events instead of just the ones which should not escape...

    An override to this should work.

    updateRoot: function(newRoot, oldRoot) {
    var me = this,...
  3. This is the JavaScript basics. Walking, where using ExtJS is the equivalent of running.

    getResourceURL: function (resourceName){

    return (this.self.URL_DOMAIN + this.self[resourceName]);...
  4. The converter on that int field is returning null, so the root ends up with a null id. And a null id means that a node is phantom.

    Phantom nodes are supposed to be client-side only. It means they...
  5. Replies
    OK, sorry about this unannounced change. The stores property has been removed.

    NodeInterface (what records become when they are part of a TreePanel) behaves a little differently from regular...
  6. Replies
    Thanks for the report! I have opened a bug in our bug tracker.
  7. Replies
    OK bob4ever, it turns out that it is correct that a combo dropdown, or date picker floats above sibling floaters when activated.

    That is what other UIs do. A dropdown is just a floater, and when...
  8. Replies
    Hm I see. It disappears.

    Well, I'm working on a proper solution for this ticket.

    Floating components should have an alwaysOnTop config and an alwaysAtBottom config which the ZIndexManager...
  9. Replies
    Should be the same for DateFields. The date picker will be glued to the form surface, and all windows will always be above it as required.
  10. Replies
    Yes, pickers (dropdowns from a field with triggers), should appear to the user as if they were inline, below all floating components.

    They are in fact floating components out of necessity because...
  11. As for just seeing the HTML, you are using a web server aren't you, not just directing your browser to your local drive?
  12. You really don't want to go down that route.

    Executing code scraped from innerHTML?

    It would be better too create an application, and the Panel subclasses that you require to be added as child...
  13. The code separation and simplification offered by MVVM coupled with data binding is a killer feature.

    You declaratively hook UI to data without having to write event handlers to modify the data in...
  14. I'd better not start dropping hostages to fortune like that... beyond my pay grade to set expectations on schedule. ;)

    I can tell you that we are aware of urgency in getting the polish right on...
  15. This has been quite a complex problem. The team think that those update events should fire on the TreeStore.

    It was a faulty upgrade that the new, unified Store/TreeStore API omitted the update...
  16. But the 'update' event still won't fire through the TreeStore.

    Because a node in a collapsed parent is not in a TreeStore
  17. I see what you mean. Node events used to fire through the TreeStore in 4.x

    The problem is that in 5.x, the TreeStore is also the View's driving Store. There's only one store involved now.

  18. You cannot collapse a group with a buffered store.

    By definition, a buffered store contains only a fragment of the dataset. It cannot know where the end of a group is.
  19. Replies
    The functionality you require is now implemented by setBox.

    setBox sees if what is passed is an Ext.util.Region, and does right things.

    The setRegion Element method interfered with binding to...
  20. Try the solution I propose in this thread:

    You then configure the TreeStore...
  21. So I have a possible solution.

    Try this override, and configure the store with

    linearLoad: true
  22. I will create a Jira ticket for it.
  23. OK, testing your fiddle against a nightly, the trigger appears as the magnifying glass, so this conflict appears to have been fixed.
  24. It's a CSS specificity conflict.

    The rule from the grid styling is winning.

    If you change the selector

    x-form-search-trigger {
  25. It would need a custom Reader, and server-generated node IDs, and then upward links, like

    parentId: 'FOO'

    In the data objects so that the tree structure can be created during read.
Results 1 to 25 of 115
Page 1 of 5 1 2 3 4