Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    #16
    This has now been fixed - you can test in builds dated July 27 and later.

    Comment


      #17
      Indeed it is fixed, but the grid filter criteria is broken.

      Here's a simple stand-alone that reproduces the problem.

      Code:
      public void onModuleLoad() {
      
              ListGrid grid = new ListGrid();
              grid.setShowFilterEditor(true);
              grid.setWidth100();
              grid.setHeight100();
              grid.addFilterEditorSubmitHandler(new FilterEditorSubmitHandler() {
      
                  @Override
                  public void onFilterEditorSubmit(FilterEditorSubmitEvent event) {
                      SC.logWarn("event.getCriteria(): " + event.getCriteria().getValues());
                  }
              });
      
              DataSourceTextField f1 = new DataSourceTextField("f1", "Field 1");
              f1.setCanFilter(true);
              DataSourceDateField f3 = new DataSourceDateField("f3", "Field 3");
              f3.setCanFilter(true);
      
              DataSource datasource = new DataSource();
              datasource.setClientOnly(true);
              datasource.setFields(f1,  f3);
              grid.setDataSource(datasource);
      
              grid.fetchData(new AdvancedCriteria(OperatorId.AND, new Criterion[]{new Criterion("f1", OperatorId.EQUALS, 1)}));
      
              grid.draw();
          }
      Just press on the date filter and select as FROM DATE: today
      Then filter and see the criteria:

      {operator=and, _constructor=AdvancedCriteria, criteria=[{fieldName=f3, operator=greaterOrEqual, value=Mon Jul 27 12:00:00 GMT+300 2015}, {operator=iContains, fieldName=fieldName, value=f1}, {operator=iContains, fieldName=operator, value=equals}, {operator=equals, fieldName=value, value=1}]}

      Something is terribly wrong with this criteria.

      SmartClient Version: v10.0p_2015-07-27/LGPL Development Only (built 2015-07-27)
      Last edited by kiril_bhd; 27 Jul 2015, 02:15.

      Comment


        #18
        Obviously, this new behavior is not a result of the recordComponent fix - it's was an unrelated issue, which is now fixed for builds dated July 28 and later.

        Comment


          #19
          Thank you for fixing it :)
          And I confirm the recordComponent fix.

          Best Regards!

          Comment

          Working...
          X