161 - SetRelativeWidth within a TabGroup misses 60 pixels

1. Create a TabGroup
2. Create an InlineGroup within the TabGroup using SetRelativeWidth( 0.7 )
3. Create a second InlineGroup within the TabGroup using SetRelativeWidth( 0.3 )

Would expect the two InlineGroups to fill the whole width of the TabGroup.
Instead there will always be 60 pixels unused space left over.

Found in Ace-Release r960, also happens in r964.

The described phenomen also happens with other widgets to be placed with SetRelativeWidth in a TabGroup.

User When Change
Nevcairiel Oct 12, 2014 at 08:43 UTC Changed status from Accepted to Declined
Nevcairiel Aug 10, 2010 at 06:12 UTC Changed status from New to Accepted
Jos_eu Aug 08, 2010 at 16:14 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Nevcairiel Nevcairiel Oct 12, 2014 at 08:42 UTC - 0 likes

    I cannot reproduce this problem (anymore?). I created a frame, with a tab group, and two inline groups, which each contain a full width button, and set the inline groups to 0.7 and 0.3 relative, and they are on the same row in the tab group and fill the entire space available as well.

  • Avatar of Nevcairiel Nevcairiel Aug 10, 2010 at 06:12 UTC - 0 likes

    There must've been some reason to use this value. I'll look into it soon(ish).

  • Avatar of Jos_eu Jos_eu Aug 09, 2010 at 19:56 UTC - 0 likes

    I searched the TabGroup code for a possible solution and maybe found one in the OnWidthSet function.

    local contentwidth = width - 60

    change to:

    local contentwidth = width - 18

    If there is no special reason behind the -60 except of reducing the contentwidth by the width of the border then 18 seems to fit better than 60.

    Last edited Aug 12, 2010 by Jos_eu


Last updated
Oct 12, 2014
Aug 08, 2010
Declined - We decided not to take action on this ticket.
Defect - A shortcoming, fault, or imperfection
Medium - Normal priority.

Reported by

Possible assignees