# Issue with sizing on screen elements **URL:** \ **Category:** Questions about Thunkable X\ **Created:** [April 26, 2020, 8:14am UTC](https://community.thunkable.com/t/issue-with-sizing-on-screen-elements/564278 "2020-04-26T08:14:40Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![henrikhngj5](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/henrikhngj5/32/67710_2.png) [@henrikhngj5](https://community.thunkable.com/u/henrikhngj5)\ **Post date:** [April 26, 2020, 8:14am UTC](https://community.thunkable.com/t/issue-with-sizing-on-screen-elements/564278/1 "2020-04-26T08:14:40Z")
I have seen a bit of strange behaviour over the weekend. I did not touch the code, but all of a sudden the screen report very small sizes upon startup. It happens only on Android using the LIVE app - not on iOS… I close my eyes and hope it works Monday… Henrik ---
**Author:** ![domhnallohanlon](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/domhnallohanlon/32/29554_2.png) [@domhnallohanlon](https://community.thunkable.com/u/domhnallohanlon)\ **Post date:** [April 26, 2020, 8:20am UTC](https://community.thunkable.com/t/issue-with-sizing-on-screen-elements/564278/2 "2020-04-26T08:20:48Z")
> [@henrikhngj5](#): > > but all of a sudden the screen report very small sizes upon startup. That sounds strange @henrikhngj5, do you mind posting a screenshot here for us to take a look at? > [@henrikhngj5](#): > > I close my eyes and hope it works Monday Hopefully we can find more…technical?..solution to this! 😂 ---
**Author:** ![henrikhngj5](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/henrikhngj5/32/67710_2.png) [@henrikhngj5](https://community.thunkable.com/u/henrikhngj5)\ **Post date:** [April 26, 2020, 9:34am UTC](https://community.thunkable.com/t/issue-with-sizing-on-screen-elements/564278/3 "2020-04-26T09:34:42Z")
Hi domhnallohanlon, I do not mind at all… Let me explain; I do a bowling app and 2 essential ingredients is the bowling pins and the scorecard. The user is supposed to touch the pins to indicate they fell and so I want to make them as big as possible to make this easier. In addition, the scorecard needs to be as big as possible, to make the final score easy to read. Ideally it should look like this [![Google Photos](https://lh3.googleusercontent.com/urno5g_eSZvyAoBVu7J0djGyHeILyvPKDgkFBGevrImqnOLbmobLFq8mtHLJXB8ZanuDMyks5qlGKhyr3m7DTdFPYdhi31l8vAbxsMMnqYreSM-wPO0kWf-W1inP0EoLVaOlupUlaQ=w600-h315-p-k "New photo by Henrik Rasmussen") ](https://photos.google.com/share/AF1QipNi-gQwwCJ6-7Hx2-8IJit_G_r0ewg8zN8MFr9VHbwwYF45xqgDm2h-BAopg2L4-g?key=eVNtOWNPX08tRFRya0xMaTdydHdySExLOTZaUW1B) and it does when I adjust the size in OnOpen. However, if I do it OnStart which I prefer, as it only dependent on the device, then it will now look like this [![Google Photos](https://lh3.googleusercontent.com/GvRS2J9KvEoRgMCutlTLaBkPwmtNVXP7H6s8ZKwgmfruzpwsReib9UW5b_PsNGZZcZfskQQRNDvH8Gp0_Ao2RP13aqwK5IZopLnxO5pYDHvq60PAnwoxR3LWjlAEeyVGF6cReUU9NA=w600-h315-p-k "New photo by Henrik Rasmussen") ](https://photos.google.com/share/AF1QipMatBE--iocBdkXAlRNkqWJdm1iF8HPkEuPYaDSruw4PjCmx-3l1TMO-uW8FJ5NUA?key=bW5ndzJ0SFV6Z3prUDI4ZWxHcjAtUEhCdDZJam93) where you can clearly see that scorecard and pins are too small, as they are computed based on my screen containers size, reported back to me as object-\>computed size This did not use to be like this, last week it was doing me well, but this weekend, it has been changed - at least for me… Henrik ---
**Author:** ![henrikhngj5](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/henrikhngj5/32/67710_2.png) [@henrikhngj5](https://community.thunkable.com/u/henrikhngj5)\ **Post date:** [April 28, 2020, 12:43pm UTC](https://community.thunkable.com/t/issue-with-sizing-on-screen-elements/564278/4 "2020-04-28T12:43:50Z")
It is still a problem for me, but I did a workaround… ---
**Author:** ![domhnallohanlon](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/domhnallohanlon/32/29554_2.png) [@domhnallohanlon](https://community.thunkable.com/u/domhnallohanlon)\ **Post date:** [April 28, 2020, 3:59pm UTC](https://community.thunkable.com/t/issue-with-sizing-on-screen-elements/564278/5 "2020-04-28T15:59:28Z")
Hey @henrikhngj5, for some reason your screenshots are not displaying any more - did you delete them by any chance? Can you re-upload them, if possible? Thanks ---
**Author:** ![henrikhngj5](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/henrikhngj5/32/67710_2.png) [@henrikhngj5](https://community.thunkable.com/u/henrikhngj5)\ **Post date:** [April 28, 2020, 5:43pm UTC](https://community.thunkable.com/t/issue-with-sizing-on-screen-elements/564278/6 "2020-04-28T17:43:31Z")
Sorry about that, to tidy cleaning… This issue is easy to reproduce. call screen-\>get-\>computed\_width in both onStart & onOpen. onStart always return 0, while onOpen return real width. This means, you cannot initialize your screen layout in onStart, but has to do it onOpen, which is not great, as this will make a delay for the user ---
**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\ **Post date:** [November 8, 2024, 11:29am UTC](https://community.thunkable.com/t/issue-with-sizing-on-screen-elements/564278/7 "2024-11-08T11:29:37Z")