Storyboard and Sprite Problems

Solar2D General Questions/Discussion
#1

We need to update our apps due to apple forcing us to. These apps were made by an outside company and I have little knowledge on using Corona.

I thought I could just build it again but we are having problems with sprite and storyboard (as i found out they are no longer supported.). I copied the legacy .lua files to my folder and was able to build the app but I can no longer see my menu buttons on my app only the background.

Is this a problem with storyboard or sprite. I tried to find information on migrating to composer but all the links i found to help with migration are now longer linked to the correct page. 

Any help on where to start to fix this problem would be appreciated.

#2

I don’t know if it will work for you but here is something I found on Wayback Machine -> https://web.archive.org/web/20150630210952/https://docs.coronalabs.com/api/library/composer/migration.html

#3

Both legacy sprites and storyboard are available on our GitHub repo:

https://github.com/coronalabs/framework-storyboard-legacy

https://github.com/coronalabs/framework-sprite-legacy

In both cases download the repo. Copy storyboard.lua and sprite.lua in the same folder with main.lua and you should be all set.

Now that said, depending on how old your apps are, they may be using the old Graphics 1.0 system and we’ve migrated to a new better way of doing display.* objects.  You can add:

graphicsCompatibility = 1,

to your config.lua (in the same place as your width and height) and it will cause Corona to behave in it’s old manner. Still make sure to throughly test your apps.

Rob

#4

Thank you both. I’ll have a look and hopefully it will fix my problem.

#5

Our app was made in 2010. Adding the 2 .lua files and the graphics compatibility code didn’t fix the problem. All graphics seem to show except any action buttons. Eg play game, sound on off. Any created buttons. Any other suggestions?

#6

We’ve changed the widget library out since 2010 as well.  

See if this code will help you. Like the others, you should just be able to drop the widget-v1.lua file in and either rename it to widget.lua or update your require statements to require widget-v1 instead of “widget”.

Rob

#7

I don’t know if it will work for you but here is something I found on Wayback Machine -> https://web.archive.org/web/20150630210952/https://docs.coronalabs.com/api/library/composer/migration.html

#8

Both legacy sprites and storyboard are available on our GitHub repo:

https://github.com/coronalabs/framework-storyboard-legacy

https://github.com/coronalabs/framework-sprite-legacy

In both cases download the repo. Copy storyboard.lua and sprite.lua in the same folder with main.lua and you should be all set.

Now that said, depending on how old your apps are, they may be using the old Graphics 1.0 system and we’ve migrated to a new better way of doing display.* objects.  You can add:

graphicsCompatibility = 1,

to your config.lua (in the same place as your width and height) and it will cause Corona to behave in it’s old manner. Still make sure to throughly test your apps.

Rob

#9

Thank you both. I’ll have a look and hopefully it will fix my problem.

#10

Our app was made in 2010. Adding the 2 .lua files and the graphics compatibility code didn’t fix the problem. All graphics seem to show except any action buttons. Eg play game, sound on off. Any created buttons. Any other suggestions?

#11

We’ve changed the widget library out since 2010 as well.  

See if this code will help you. Like the others, you should just be able to drop the widget-v1.lua file in and either rename it to widget.lua or update your require statements to require widget-v1 instead of “widget”.

Rob