Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Are you sure that it's called automatically or do you have code in your widget that calls it?</p> <p>It's good practice to call it since it sets <code>_started</code> to <code>true</code> which is used by quite a few widgets for determining behavior and/or layout. Most widgets require that you call it (as you've seen).</p> <p><code>startup</code> is heavily used by composite widgets that need to control sub-widgets. </p> <p>Basically, anything that inherits from <code>dijit._Widget</code> should call startup after instantiation.</p> <p><strong>EDITS:</strong></p> <p>There's an <a href="http://www.sitepen.com/blog/2007/11/13/dissecting-dijit/" rel="nofollow noreferrer">article on SitePen</a> about the dijit lifecycle which discusses startup a bit in the article itself and in the comments. It's over two years old though and I think things have changed.</p> <p>The <a href="http://books.google.com/books?id=PgK1GbyiiDUC&amp;pg=PA341&amp;lpg=PA341&amp;dq=dijit+startup&amp;source=bl&amp;ots=6mtKbCG2vS&amp;sig=cmEW74yQnUgSUBJ9zpPZ3J2bKTo&amp;hl=en&amp;ei=_tSKSuePHYvOlAfglIwu&amp;sa=X&amp;oi=book_result&amp;ct=result&amp;resnum=5#v=onepage&amp;q=dijit%20startup&amp;f=false" rel="nofollow noreferrer">O'Reilly dojo book</a> also talks about startup but it says it should be called on containiner widgets. I've had to call it on the grid though so that doesn't make sense either.</p> <p>It doesn't really hurt anything by calling it (unless you call it before children are added to your widget). I'd say always call it.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload