Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: Store debugging help

  1. #1
    Sencha Premium Member steffenk's Avatar
    Join Date
    Jul 2007
    Location
    Haan, Germany
    Posts
    2,675

    Default Store debugging help

    Hi,

    i need some help how to debug a store.
    In my case, with one url the store is filled after load with data.items, with another url it's empty. Now i need to know what went wrong. I think i have to debug inside Reader. What is the best practise without breakpoints in ext_all?
    vg Steffen
    --------------------------------------
    Release Manager of TYPO3 4.5

  2. #2
    Sencha User Animal's Avatar
    Join Date
    Mar 2007
    Location
    Bédoin/Nottingham
    Posts
    30,890

    Default

    You mean ext-all-debug of course.

    Search for the function, set the breakpoint, run.

  3. #3
    Sencha Premium Member steffenk's Avatar
    Join Date
    Jul 2007
    Location
    Haan, Germany
    Posts
    2,675

    Default

    hm - as i wrote i didn't want to step over so much code in ext-all-debug. When i debug the store after load i see what is filled and what not. I can see that my fields are filled correct, but data is empty.

    So i want to break it down, and want to ask how you do such debug: in a callback function, override reader or ...
    vg Steffen
    --------------------------------------
    Release Manager of TYPO3 4.5

  4. #4
    Sencha User Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,245

    Default

    The callback function returns the most complete information (it's called for both success and failure).

    If you don't want to define a callback for every store you could use class level listeners for stores (Ext 3 only).

  5. #5
    Sencha Premium Member steffenk's Avatar
    Join Date
    Jul 2007
    Location
    Haan, Germany
    Posts
    2,675

    Default

    Hi,

    i have a further question.

    when i use ext-all-debug there should be the console available with ctrl + shift + home
    But it never popups. When i look at the example (which works) i see no other magic. What can be the problem? (no js error at all) Is there an alternative way to open the console?
    vg Steffen
    --------------------------------------
    Release Manager of TYPO3 4.5

  6. #6
    Sencha User Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,245

    Default

    Ext 3.0.0 ext-all-debug.js doesn't contain src/debug.js. You'll have to include the file separately.

  7. #7
    Sencha Premium Member steffenk's Avatar
    Join Date
    Jul 2007
    Location
    Haan, Germany
    Posts
    2,675

    Default

    ah - thx. For what reason was it excluded?

    Edit: tested and doesn't work either. I don't find the key handler calling it. Also manual call of createConsole() brings up an error. Do i miss something?
    vg Steffen
    --------------------------------------
    Release Manager of TYPO3 4.5

  8. #8
    Sencha User Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,245

    Default

    It was excluded by accident (the current build process makes ext-all-debug and ext-all completely the same, so the build process would have to be modified).

    You did include src/debug.js or examples/debug/debug.js (the second one has a bug)?

  9. #9
    Sencha Premium Member steffenk's Avatar
    Join Date
    Jul 2007
    Location
    Haan, Germany
    Posts
    2,675

    Default

    Hi,

    i included src/debug.js as you suggested.
    vg Steffen
    --------------------------------------
    Release Manager of TYPO3 4.5

  10. #10
    Sencha Premium Member steffenk's Avatar
    Join Date
    Jul 2007
    Location
    Haan, Germany
    Posts
    2,675

    Default

    sorry for pushing again, but i'm not able to open the debug console.
    When i look to the debug example, it includes own debug.js. But i don't get how it's appended to the border layout.

    So how can i manually open the console, eg in a Wxt.window, any suggestions?
    vg Steffen
    --------------------------------------
    Release Manager of TYPO3 4.5

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •