Announcement

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

    TextItem with KeyPressFilter return old value

    Hello,

    We upgraded our application from 4.0p (NIGHTLY 2014-02-12) to 5.0p (NIGHTLY-2015-04-03) and we hawe some issues with a TextItem associated with a KeyPressFilter. If you run following code

    Code:
    	public void onModuleLoad() {
    
    		DynamicForm form = new DynamicForm();
    		form.setWidth(200);
    		form.setHeight(200);
    		
    		TextItem item = new TextItem();
    		
    		item.setTitle("item0");
    		item.setKeyPressFilter("[0-9]");
    		item.setValue(2015);
    		
    		item.addKeyPressHandler(new KeyPressHandler() {
    			
    			@Override
    			public void onKeyPress(KeyPressEvent event) {
    				GWT.log("current value " + event.getItem().getValue());
    			}
    		});
    		
    		
    		form.setFields(item);
    		form.draw();
    	}
    item will be initially filled with value 2015.
    Execute these steps:

    * with cursor at the end press backspace (value will be 201)
    * press number 6: log will show the old value (2015) instead of displayed value (201)

    With SmartGWT 4.0p20140212 when you press number 6 log show current item value (201).
    Is this a missing setting or a wrong behavior?

    Browser Chrome 41.0.2272.118 (64-bit)

    Thanks in advance

    #2
    key press handler returns old value

    Hi,

    I have the same issue.
    I have investigated the issue and I noticed that if I remove the keypressfilter the keypresshandler gives me back the new value and not the old.

    Can someone please help me?

    best regards

    thanks in advance

    Comment


      #3
      We are looking into this and will follow up when we have more information.

      Regards
      Isomorphic Software

      Comment


        #4
        We've made a change to address this issue. Please try the next nightly build, dated April 15 or above (5.0 or 5.1 branches)

        Regards
        Isomorphic Software

        Comment


          #5
          Issue fixed

          The issue is resolved in nightly build 5.0p 15/04/2015.
          Thank you very much.

          Comment

          Working...
          X