Home/ Questions/Q 3661538
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T01:18:59+00:00

I think I understand the difference between _create and _init in widget definitions (see

  • 0

I think I understand the difference between _create and _init in widget definitions (see for instance this question), but I’m still not certain about the purpose for the distinction. What sorts of setup tasks go in _create() or in _init()? What goes wrong if the widget author chooses the wrong one?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From:

    Use _create to build and inject
    markup, bind events, etc. Place
    default functionality in _init().
    The dialog widget, for example,
    provides an autoOpen parameter
    denoting whether or not the dialog
    should be open once the widget is
    initialized; a perfect spot for
    _init()!

    Also:

    The widget factory automatically fires
    the _create() and _init() methods
    during initialization, in that order.
    At first glance it appears that the
    effort is duplicated, but there is a
    sight difference between the two.
    Because the widget factory protects
    against multiple instantiations on the
    same element, _create() will be
    called a maximum of one time for each
    widget instance, whereas _init() will
    be called each time the widget is
    called without arguments…

    If the author uses _init() when _create() should have been coded, the result will be that the code in _init() will be executed once per widget instantiation.

    • 0