Search Type: Posts; User: dongryphon

Page 1 of 5 1 2 3 4

Search: Search took 0.04 seconds; generated 10 minute(s) ago.

  1. I am not seeing this in the button example odd... Can you tell from the style inspector what rule is causing that border?
  2. The Ext.elevateFunction is an optional, user-supplied method that we route through on re-entry from the browser. This was added to "elevate" application code to escape contexts like those for Windows...
  3. Thanks for the report! Your change is probably one we can make - opening a ticket to look into it.
  4. Looks like the build agent problem did not get fixed today, so I ran up Cmd to the beta channel. It is not an official beta just a nightly build.


    sencha upgrade --beta

  5. First off, I noticed that the Ext JS version was wrong updated to 5.1.2 (should be 5.1.1 of course) - that should be fixed now for next nightly. On the other part, the Cmd nightly build agent went...
  6. From a Cmd perspective, you are correct. Since Cmd has full file system access, we could indirect to a common location on the system very easily.

    But it is the browser that has to load the Ext JS...
  7. Thanks for the report! I have opened a bug in our bug tracker.
  8. Thanks for the report! I have opened a bug in our bug tracker.
  9. What is the value of "Ext.isReady" ? It should become true once all dynamically loaded files are loaded and the document is ready. I suspect there is something blocking this or else the launch method...
  10. Sorry about that - moved to the proper Ext 5 Bugs forum this time.
  11. The difference is that a load can result in 0 records so isLoaded cannot be based on number of records.
  12. It would be simple in some cases in Java but in Ant it is a lot less clean to use an expansion vs "/" ... so we made the call to not muck up the Ant code with that concern. Glad to hear it isn't...
  13. Thanks for the report! I have opened a bug in our bug tracker.
  14. Fiddle
  15. @t.nissen -

    Good to hear and yes Cmd (GA) is required for Ext JS (GA).

    For the other issue, I would first see what context those exceptions are coming from. Those lines by...
  16. Replies
    The autoCreateViewport config is still supported though you can replace it with "mainView" in 5.1. The docs should be updated to use "mainView" in the near future. Only the getAutoCreateViewport...
  17. In general you are correct about \'s vs /'s in paths. As it turns out, the Windows API does accept /'s as path separators. See...
  18. Replies
    The GPL info messages seem to be incorrect but should be cleaned up. The callSuper warnings are not supposed to be enabled for Sencha Touch and are not indicating a problem... but again should be...
  19. Replies
    Thanks for the report! I have opened a bug in our bug tracker.
  20. Have you run sencha app upgrade? I suspect you have an old bootstrap.

    If you have, you might try a clean build:

    sencha app build --clean development
  21. Thanks for the report! I have opened a bug in our bug tracker.
  22. @Alinanila -

    As Greg said, the exclude command is what you will want here. From the SDK folder you can run sencha compile commands and Cmd will understand that the context is that SDK.

  23. I cannot speak directly to Architect but from Cmd perspective the issue is location of the web root. The amount of relative path navigation that can be done before we depart the web root is unknown,...
  24. I've moved this to its own thread in Ext JS Bugs forum. The launch method should certainly be called.

    Officially, Sencha Architect does not yet support Ext JS 5.1, so there may be some issue that...
  25. Replies
    The only "me" variable in v4 is one you would have provided by adding your own logic to an initComponent implementation or similar. Of course, you can still do that in v5. In other words, there is no...
Results 1 to 25 of 118
Page 1 of 5 1 2 3 4