Several solutions have been proposed to use this new build and its color handling. You can:

– create a function to convert your colors

– divide each element by 255 like this: local back:setStrokeColor(25/255, 25/255, 25/255)

– throw up your hands and run your app in compatibility mode

The first two introduce overhead in terms of processing, which we really don’t need if we want to optimize our app’s speed. Using compatibility mode isn’t a great idea either as eventually it’s sure to be deprecated.

“The first two introduce overhead in terms of processing, which we really don’t need if we want to optimize our app’s speed.”

Matt,
Your script stores the named colors in a table. Why not just do away with the runInGraphics2 function and store the colors as percent in another table. This would avoid the computational cost that is mentioned in the post.

Because I ripped the values off a web page and regularly update it with as little hassle as possible. The conversion function only runs once, at the start of runtime so the computational cost is nil for runtime.

Thank you for this tip, Matt! Clearly there’s a lot to learn with Gfx2. I struggled with some of the layout challenges and the concept of ‘snapshots’ etc. Maybe I’ll take it bit by bit and try to write more tutorials as I get through it.

Hi, that is my SevenMinutes app, which you can download in all its glory using these links: http://www.ladeezfirstmedia.com/apps/sevenminutes. There are some screenshots there as well. It’s a basic app with background color, a rectangle at the top with some buttons, and a tabBar widget at the bottom. Thanks for your kind words!