• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Grid layout getting clipped as form is resized

Stats

  • Replies 5
  • Subscribers 150
  • Views 290
  • Members are here 0

Grid layout getting clipped as form is resized

SZ20260803361
SZ20260803361 18 days ago

Hello,

I have run into a new issue. Inside my UI built with hiCreateHorizontalBoxLayout within a hiCreateLayoutForm, there are seven buttons arranged via hiCreateGridLayout as shown below:

hiCreateGridLayout( 'gridLayout_button
    ?items (list 
        list( button_1 'row 0 'col 0 )
        list( button_2 'row 0 'col 1 )
        list( button_3 'row 1 'col 0 )
        list( button_4 'row 1 'col 1 )
        list( button_5 'row 2 'col 0 )
        list( button_6 'row 2 'col 1 )
        list( button_7 'row 3 'col 0 )
        list( 'col_min_width 0 5)
        list( 'col_min_width 1 5)
    )
)

I have specified the minimum column widths using list( 'col_min_width 0 5) and list( 'col_min_width 1 5). However, when I drag the right‑hand border of the form with the mouse to shrink the window width, the button widths do not shrink accordingly. Instead, the button sizes remain unchanged and get progressively clipped as the form narrows.

My form creation code:

hiCreateLayoutForm(
    formName "LAYOUT_DEMAND" boxLayout_ver
    ?minSize list(30 200)			 
)

  • Sign in to reply
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett 18 days ago

    Please read Guidelines for the Custom IC SKILL Forum which asks you not to post new (unrelated) questions on the same thread. I split it into a separate thread for you - but in future, please post a new thread when you have a new question.

    I don't seem to be able to post my example code which showed this (since your code was not complete), but everything seems to work fine. As I make the form bigger:

    Then smaller:

    Then smaller again:

    Once the buttons reach their minimum size (to display the buttonText) they don't get any smaller (despite the minimum column width) and scrollbars appear instead. I would not expect the button text to get clipped.

    This all seems reasonable to me.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett 18 days ago

    Please read Guidelines for the Custom IC SKILL Forum which asks you not to post new (unrelated) questions on the same thread. I split it into a separate thread for you - but in future, please post a new thread when you have a new question.

    I don't seem to be able to post my example code which showed this (since your code was not complete), but everything seems to work fine. As I make the form bigger:

    Then smaller:

    Then smaller again:

    Once the buttons reach their minimum size (to display the buttonText) they don't get any smaller (despite the minimum column width) and scrollbars appear instead. I would not expect the button text to get clipped.

    This all seems reasonable to me.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett 18 days ago in reply to Andrew Beckett

    Trying again to post the code from above:

    let((button_1 button_2 button_3 button_4 button_5 button_6 button7 boxLayout_ver)
      button_1=hiCreateButton(?name 'button_1 ?buttonText "Button 1")
      button_2=hiCreateButton(?name 'button_2 ?buttonText "Button 2")
      button_3=hiCreateButton(?name 'button_3 ?buttonText "Button 3")
      button_4=hiCreateButton(?name 'button_4 ?buttonText "Button 4")
      button_5=hiCreateButton(?name 'button_5 ?buttonText "Button 5")
      button_6=hiCreateButton(?name 'button_6 ?buttonText "Button 6")
      button_7=hiCreateButton(?name 'button_7 ?buttonText "Button 7")
      boxLayout_ver=hiCreateGridLayout( 'gridLayout_button
        ?items (list 
            list( button_1 'row 0 'col 0 )
            list( button_2 'row 0 'col 1 )
            list( button_3 'row 1 'col 0 )
            list( button_4 'row 1 'col 1 )
            list( button_5 'row 2 'col 0 )
            list( button_6 'row 2 'col 1 )
            list( button_7 'row 3 'col 0 )
            list( 'col_min_width 0 5)
            list( 'col_min_width 1 5)
        )
      )
      hiCreateLayoutForm(
        'myForm "LAYOUT_DEMAND" boxLayout_ver
        ?minSize list(30 200)			 
      )
      hiDisplayForm(myForm)
    )
    

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • SZ20260803361
    SZ20260803361 18 days ago in reply to Andrew Beckett

    Hi Andrew,

    Appreciate you splitting the thread! My bad for bundling different questions together. I’ve gone through the forum guidelines and will start fresh threads for new topics from now on.


    Figure 1 shows the form fully displayed after stretching the window to the right.


    Figure 2 shows the form as it appears right after loading.

    My apologies — I should have shown the complete form to avoid confusion. As you can see in Figure 1 and Figure 2, my expectation is that all fields would be fully visible immediately upon‑loading (like Figure 2). What actually happens is I have to drag the right border of the form to reveal all fields (as shown in Figure 1). I suspect this behavior may be related to the presence of cycle‑field and string‑field widgets.




    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 18 days ago in reply to SZ20260803361

    This was recently discussed in How to get the size of a custom dockable window. There's a link to an article in that thread that gives a (rather clunky) workaround. As I advised in that thread, you might want to contact customer support and ask for a duplicate of the CCR to be filed on your behalf to increase the visibility and hopefully the priority.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • SZ20260803361
    SZ20260803361 17 days ago in reply to Andrew Beckett

    OK, thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information