Floating menus > Item Spacing > Padding Top

Padding controls are not working as expected. It seems that this property has been broken during last release versions.

I have an item menu in my setup with dimensions = width 45 x height 58

If I set "Padding Top" to 0, the icon is shown in the middle of the floating menu.
If I set "Padding Top" to 1, the icon is shown in the bottom of the floating menu.
If I set "Padding Top" to 30, the icon is shown in the bottom of the floating menu.

So there is no difference between 1 and 30, the result is the same.

Here are some screenshots to see this problem:

weird, what is the item size set to in your case?

Ahh I think I see the issue. It's happening if the bottom or top padding is set to 0. I'll fix that.

//edit: weird no, I don't think that's it.


Could you maybe copy & paste the item where 1 and 30 result in the same? Is maybe the height of the item just set to a high value? Maybe try setting to "fit content" instead

FYI, using BTT v 4,765 and Macbook Pro Ventura 13.7

The item size is width 45 x height 58

This item is not a new item. I did it months ago and setting it to paddding 30 it was placed near the bottom.

This item menu is part of a floating menu with 4 items. The 4 items should be aligned near the bottom with a top padding=30

Regarding copy it, do I copy the floating menu and the 4 menu items? Do I paste them here in the thread?

there was a recent bugfix for padding that might cause this. Previously there was always some padding added implicitly and there was no way to disable that. Now if the padding is set to 0, it should really be zero. I'll check whether I can reenable this old behavior for items that have been created with previous BTT versions!

Just to be sure you understand my issue.

When top padding is set to zero, it works as expected.

The problem is when I set any other positive value, the padding is set to the maximum, to the bottom...

Ah! I think now I can reproduce what you are seeing. I'll have a look!

Great!

Would be great if you'd check with 4.768 (building & uploading now)

Yes, I try it now and report back

v4,768 has fixed it, great!

Thanks for going so fast!!

1 Like