Results 1 to 3 of 3

Thread: Bug in Sencha Designer 2 when using Button Handrer Vs. Listener

  1. #1
    Sencha User
    Join Date
    Feb 2011
    Posts
    33
    Vote Rating
    0
      0  

    Default Bug in Sencha Designer 2 when using Button Handrer Vs. Listener

    Hello!
    I was following the video tutorial "Getting Started with Sencha Touch 2" http://vimeo.com/37974749 that is based in the Building your First App.

    I really think there is a BUG in Sencha Designer when using a form button. Please watch the video to have an idea of the problem:

    Sencha Designer 2 Problem - Button Handler Vs. Listener
    http://www.youtube.com/watch?v=78qjrFiC5gY

    Thanks!

  2. #2
    Sencha User aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,487
    Vote Rating
    145
      0  

    Default

    When defining a class you use the userAlias. userAlias encompasses a number of different types, including xtypes. (when views and defined for xtypes are used it will automatically prefix with "widget.")

    One of the benefits of using an event instead of a handler function is the fact that the this object will automatically be in the scope of the class you defined. In other words you don't have to do this.up() to find the class. You are already in the scope of the form.

    You can delete the up() call.
    Aaron Conran
    @aconran

  3. #3
    Sencha User
    Join Date
    Feb 2011
    Posts
    33
    Vote Rating
    0
      0  

    Default

    Thanks!

Posting Permissions

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