Results 1 to 3 of 3

Thread: Destroy appLoadingIndicator element

    Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format.
  1. #1
    Ext JS Premium Member Steffen Hiller's Avatar
    Join Date
    Mar 2008
    Posts
    786
    Vote Rating
    36
      0  

    Default Destroy appLoadingIndicator element

    I think the framework should destroy the appLoadingIndicator element automatically after the app is initiated, since it unnecessarily keeps using (pretty heavily actually) the CPU while the app is running.

    One official ST example (particles) is already doing the same thing I do in my app launch method:

    Code:
    Ext.fly('appLoadingIndicator').destroy();

  2. #2
    Sencha - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    39,553
    Vote Rating
    1272
      0  

    Default

    What if you wanted to keep the indicator around while sending a request to a server to see if a user is logged in? There are uses to allow the dev to destroy it when he/she chooses.
    Mitchell Simoens @LikelyMitch
    Sencha Inc, Senior Software Engineer
    ________________
    Learn BBCode and use it! Checkout the CODE tag!

    Check out my GitHub, lots of nice things for Ext JS and Sencha Touch
    https://github.com/mitchellsimoens

  3. #3
    Ext JS Premium Member Steffen Hiller's Avatar
    Join Date
    Mar 2008
    Posts
    786
    Vote Rating
    36
      0  

    Default

    I'd imagine that you could add it to the painted event of the ext viewport or something?
    Then your viewport wouldn't be painted until that user auth request is made?

Posting Permissions

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