ui.lua in Corona Simulator 919 and 922

[thegdog]

I’ve got a project using version 2.4 of the ui.lua (http://developer.coronalabs.com/code/enhanced-ui-library-uilua).

In Corona build 894, the buttons (which are coded as onPress) work fine.

In Corona builds 919 and 924, the buttons (coded as onPress) cause the Simulator to unexpectedly close. Building it for the iPad, the app just crashes and disappears. If I change the buttons to onEvent, the same thing happens.

If I change the buttons to onRelease, the button click doesn’t crash the Simulator and the app continues on.

Any thoughts why this would be happening? Anyone else experiencing the same thing? [import]uid: 17827 topic_id: 31358 reply_id: 331358[/import]

[peach_pellen]

Hey there - have you submitted a bug report? If you haven’t could you please do so and include a sample that shows the problem? It would be a big help when we are looking into it and establishing if there is indeed an issue here (and it sounds like there is) that we need to address. [import]uid: 52491 topic_id: 31358 reply_id: 125383[/import]

[thegdog]

Peach,
I did not file a bug report. Wasn’t sure where the problem was, so thought I would see if anyone else had experienced it.

I ended up ripping out the UI library and switching over to the included button widget, and just added in my own code to do the isActive functionality that the widget doesn’t provide, but UI did.

But I will see if I can build a test app with the problem in the next few days and submit the bug report. [import]uid: 17827 topic_id: 31358 reply_id: 125395[/import]

[thegdog]

I will say that the two things that surprised me about switching over to using the button widget instead of UI:

1. The output file for my app using the ui.lua file was 18.1 MB. Using widget, it is 18.5 MB. I was thinking it would be smaller, but I guess the widget library actually adds more code.

2. Load time increased, albeit by just a second or two on a first gen iPad. I don’t know that I was expecting any difference, but it did surprise me.

Otherwise, everything seems to be working fine moving over to the button widget after some refactoring. [import]uid: 17827 topic_id: 31358 reply_id: 125397[/import]

[peach_pellen]

Edit: Have just been advised that ui.lua is no longer supported, the widget library is intended to be used instead… [import]uid: 52491 topic_id: 31358 reply_id: 125398[/import]

[peach_pellen]

Hey there - have you submitted a bug report? If you haven’t could you please do so and include a sample that shows the problem? It would be a big help when we are looking into it and establishing if there is indeed an issue here (and it sounds like there is) that we need to address. [import]uid: 52491 topic_id: 31358 reply_id: 125383[/import]

[thegdog]

Peach,
I did not file a bug report. Wasn’t sure where the problem was, so thought I would see if anyone else had experienced it.

I ended up ripping out the UI library and switching over to the included button widget, and just added in my own code to do the isActive functionality that the widget doesn’t provide, but UI did.

But I will see if I can build a test app with the problem in the next few days and submit the bug report. [import]uid: 17827 topic_id: 31358 reply_id: 125395[/import]

[thegdog]

I will say that the two things that surprised me about switching over to using the button widget instead of UI:

1. The output file for my app using the ui.lua file was 18.1 MB. Using widget, it is 18.5 MB. I was thinking it would be smaller, but I guess the widget library actually adds more code.

2. Load time increased, albeit by just a second or two on a first gen iPad. I don’t know that I was expecting any difference, but it did surprise me.

Otherwise, everything seems to be working fine moving over to the button widget after some refactoring. [import]uid: 17827 topic_id: 31358 reply_id: 125397[/import]

[peach_pellen]

Edit: Have just been advised that ui.lua is no longer supported, the widget library is intended to be used instead… [import]uid: 52491 topic_id: 31358 reply_id: 125398[/import]

[magadistudio]

Hello Peach,

I am having some issues with the scrollView which I use to create horizontal menu slide just like https://itunes.apple.com/us/app/pickles-paper-dolls-lite/id492250386?mt=8, which is triggered, and populated when the top buttons is selected. Just like the game above. For some reason, in the iPad the game crushes without any warnings… nothing! I know I am doing something wrong.

I am also using ui.lua library for the buttons inside the scrollView Corona widget. I have tried to get rid of ui.lua library, and created buttons using Corona newButton widget but still having the same issue. So that makes me think that it must be something else breaking things.

Do you have any suggestions?

Thanks in advance. [import]uid: 75258 topic_id: 31358 reply_id: 128894[/import]

[magadistudio]

Hello Peach,

I am having some issues with the scrollView which I use to create horizontal menu slide just like https://itunes.apple.com/us/app/pickles-paper-dolls-lite/id492250386?mt=8, which is triggered, and populated when the top buttons is selected. Just like the game above. For some reason, in the iPad the game crushes without any warnings… nothing! I know I am doing something wrong.

I am also using ui.lua library for the buttons inside the scrollView Corona widget. I have tried to get rid of ui.lua library, and created buttons using Corona newButton widget but still having the same issue. So that makes me think that it must be something else breaking things.

Do you have any suggestions?

Thanks in advance. [import]uid: 75258 topic_id: 31358 reply_id: 128894[/import]