No gaps between buttons except for default shape

[btnsjen]

Hello, some help would be very welcome.

Although the buttons are correctly separated by gaps on the AppInventor Designer, independent of the button shape, still on the phone, both via the companion app and also using my generated app, gaps only appear for the default shape. Gaps missing even for rectangular=2, that is expected to behave identical to default=0 .

In my app, identical behaviour for static buttons and also for buttons created by CompCreator.
Same missing gaps when using horizontal arrangements for each row, within vertical arrangement.

Using Android 12, Companion App 2.76.

Below is the screen from the phone, upper half static buttons, lower half dynamic. In my real app I want to use CompCreator to allow selecting buttons arrangement.

Searched the archive, found suggestions to avoid TableArrangements, and others to separate using labels.

Tried this as work-around. It is rather poor solution, because:

• this doubles the number of graphical elements
• still worse, too complicated to compute button sizes. For example, two buttons 45% each, with 10% label to separate, clearly overflows 100%. In turn, without embedded Labels, row width 50% + 50% = 100% .

Here is a demo aia:

BtnGapMissing_copy.aia (73.9 KB)

Thanks in advance

[Kevinkun]

you may add margin for the buttons when you create them dynamically.
for example, use extension like this

[btnsjen]

Thank you very much. Adds margins fine.
Still must reduce buttonwidth%/height% with an unknown magic number

[TIMAI2]

Try fill parent?

[btnsjen]

Thank you very much, I can go with this. Magic number -2 is something I'd have never thought of .

[Anke]

@btnsjen

Magic number -2 is something I'd have never thought of

How can I get any details of my app crash?

Height and Width have the following interpretations: Non-negative values indicate a specific pixel value for the dimension. For negative values, there are three potential interpretations. -1 indicates Automatic, -2 means Fill Parent, and values < -1000 are used to encode percentages, e.g. 75% = -1075. For any property in App Inventor, we don’t store the value if it is the default value. This keeps the files smaller, which decreases the time to load/process/save files.

[btnsjen]

Anke, thank you very much. My preceding search for "width AND negative" produced too many results, with none of the first pages having any relevance