Announcement

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

    Resizing fonts/controls causes scrollbar to be displayed.

    Isomorphic,

    I have a form with a TextAreaItem that expands to fill the height of the form. This works as expected when using the default font/control size, however, increasing the font/control size causes a scrollbar to be displayed.

    Click image for larger version

Name:	scrollbar.JPG
Views:	34
Size:	12.4 KB
ID:	265541

    The follow entry point can be used to reproduce the issue.


    Code:
    @Override
    public void onModuleLoad() {
        Canvas.resizeFonts(2);
        Canvas.resizeControls(2);
    
        HLayout mainLayout = new HLayout();
        mainLayout.setWidth("50%");
        mainLayout.setHeight("50%");
    
        VLayout detailsLayout = new VLayout();
    
        CheckboxItem item1 = new CheckboxItem("Item1");
        item1.setLabelAsTitle(true);
    
        SelectItem item2 = new SelectItem("Item2");
    
        TextAreaItem item3 = new TextAreaItem("Item3");
        item3.setWidth("*");
        item3.setHeight("*");
    
        DynamicForm form = new DynamicForm();
        form.setNumCols(1);
        form.setHeight("*");
        form.setPadding(2);
        form.setCellPadding(3);
        form.setTitleOrientation(TitleOrientation.TOP);
        form.setItems(item1, item2, item3);
    
        VLayout formLayout = new VLayout();
        formLayout.setPadding(3);
        formLayout.setMembersMargin(15);
        formLayout.setCanHover(Boolean.FALSE);
    
        formLayout.addMember(form);
    
        TabSet tabSet = new TabSet();
        tabSet.setPaneMargin(3);
        Tab tab1 = new Tab("Tab1");
        tab1.setPane(formLayout);
        tabSet.addTab(tab1);
        detailsLayout.addMember(tabSet);
    
        mainLayout.addMember(detailsLayout);
        mainLayout.show();
    }
    SmartClient Version: v12.1p_2020-09-29/Pro Deployment (built 2020-09-29)

    Thanks

    #2
    Hi Isomorphic,

    Have you had a chance to review this?

    Thanks

    Comment


      #3
      Sorry for the delay, we have been able to reproduce the problem and we're looking at the best way to solve it.

      Comment


        #4
        We've made a change to address this.

        Please retest with a build dated June 12 or later.

        Comment


          #5
          A quick update on this report - the change we applied on June 11 addresses this issue in 13.0, but doesn't fully work on 12.1.

          We're revisiting the problem today and will update here shortly.

          Comment

          Working...
          X