Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

    Success! Looks like we've fixed this one. According to our records the fix was applied for a bug in our system in a recent build.
  1. #1
    Ext GWT Premium Member icfantv's Avatar
    Join Date
    Sep 2011
    Location
    Superior, CO
    Posts
    411
    Vote Rating
    21
    icfantv will become famous soon enough icfantv will become famous soon enough

      0  

    Exclamation ArrayIndexOutOfBoundsException on NumberField<T>.setAllowDecimals

    ArrayIndexOutOfBoundsException on NumberField<T>.setAllowDecimals


    Here's the code:

    Code:
    import com.google.gwt.core.client.EntryPoint;
    import com.sencha.gxt.widget.core.client.form.NumberField;
    import com.sencha.gxt.widget.core.client.form.NumberPropertyEditor;
    
    
    public class MainEntry implements EntryPoint {
    
    
      @Override
      public void onModuleLoad() {
        
        NumberField<Integer> integerField =
          new NumberField<Integer>(new NumberPropertyEditor.IntegerPropertyEditor());
        integerField.setAllowDecimals(false); // throws an exception
      }
    }
    In theory, I think a developer might expect the allowDecimals property to be set implicitly to false because he/she is specifying an integer type with an integer property editor and integers are whole numbers.

    If I don't call setAllowDecimals the field allows the . character which as previously mentioned violates the premise of having an integer field.

  2. #2
    Ext GWT Premium Member icfantv's Avatar
    Join Date
    Sep 2011
    Location
    Superior, CO
    Posts
    411
    Vote Rating
    21
    icfantv will become famous soon enough icfantv will become famous soon enough

      0  

    Default


    Fixed in beta 3 per release notes:

    [EXTGWT-1350] - Exception is thrown when setting allow decimals to false on a NumberField