# Setting a button's Border radius dynamically; cloning images speed

**URL:** <https://community.thunkable.com/t/setting-a-buttons-border-radius-dynamically-cloning-images-speed/1041737>\
**Category:** Questions about Thunkable X\
**Tags:** any-component\
**Created:** [December 25, 2020, 11:54pm UTC](https://community.thunkable.com/t/setting-a-buttons-border-radius-dynamically-cloning-images-speed/1041737 "2020-12-25T23:54:19Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Deluxe](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/deluxe/32/30016_2.png) [@Deluxe](https://community.thunkable.com/u/Deluxe)\
**Post date:** [December 27, 2020, 11:10am UTC](https://community.thunkable.com/t/setting-a-buttons-border-radius-dynamically-cloning-images-speed/1041737/11 "2020-12-27T11:10:36Z")

</div>

I just noticed something interesting about your test app’s code (barely visible at the end of your video). Why do you use the “repeat \> until” loop? If you want to show the clones as they get created, insert the wait block in or right under the clone block. I don’t see why you need the “repeat \> until” loop.

 ![image](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/e/e/ee1251a89789c119f9a2082004d384295685ef13.jpeg)

Just curious…

---

_[View the full topic](https://community.thunkable.com/t/setting-a-buttons-border-radius-dynamically-cloning-images-speed/1041737)._