Announcement

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

    How to make validation error to be displayed after hint ?

    I have the following code:
    Code:
    private final IntegerItem accountLockoutThreshold = new IntegerItem();
    accountLockoutThreshold.setTitle( "Account Lockout Threshold" );
            accountLockoutThreshold.setWidth( TABLE_WIDTH );
            accountLockoutThreshold.setTextAlign( Alignment.RIGHT );
            accountLockoutThreshold.setLength( 3 );
            accountLockoutThreshold.[B]setHint( "<nobr>" + "times" + "</nobr>" );[/B]
            accountLockoutThreshold.setRequired( true );
            accountLockoutThreshold.setDefaultValue( 5 );
            accountLockoutThreshold.setValidators( getIntValidator(), getRangeValidator( 1, 99 ) );
            accountLockoutThreshold.setColSpan( 3 );
            accountLockoutThreshold.setEndRow( true );
    The field has hint that displayed after the field. if during validation one of the validators failed the error is displayed UNDER the hint, pushing the hint up - see the attached image:
    Click image for larger version

Name:	hint.png
Views:	133
Size:	8.6 KB
ID:	240050
    Is it possible to make the error to be displayed AFTER the hint ?
    Attached Files

    #2
    This is not currently possible via a simple configuration property, but on reflection we agree that it would be preferable to have the error icon not wrap under the hint text.
    Let us know which version of SmartGWT you're using, and we'll look at making a change to the framework to achieve this.

    Regards
    Isomorphic Software

    Comment


      #3
      We've made a change which should address this issue in both the 11.1 and 11.0 branches. Please try the next nightly build, dated Sep 6 or above.

      Regards
      Isomorphic Software

      Comment


        #4
        I use the following version:
        SmartClient Version: v10.1p_2016-08-05/PowerEdition Deployment (built 2016-08-05)
        Can the issue be addressed in this version as well ?

        Comment


          #5
          We're looking at back porting it to that branch. We'll follow up here when we get this done

          Regards
          Isomorphic Software

          Comment


            #6
            The fix has been back ported to the 10.1 branch. Please try the next nightly build, dated September 07.

            Regards
            Isomorphic Software

            Comment

            Working...
            X