Migration issues

I just installed the latest corona build (Version 2013.2100 (2013.12.7)) and we have run into problems.

I am unable to get the graphics library to work in compatibility mode, the legacy widget Library (version 1) now doesn’t function properly either. I now get a large white mask where the scrollview is (even though I have listed it as having an alpha value of 0) and the tabBar also fails to find the gradient when indicated.

I have included my slightly modified widget library and Gradient call (In regards to the tabBar)

 local options = options or {} local id = options.id or "widget\_scrollView" local left = options.left or 0 local top = options.top or 0 local width = options.width or (display.contentWidth-left) local height = options.height or (display.contentHeight-top) local scrollWidth = options.scrollWidth or width local scrollHeight = options.scrollHeight or height local friction = options.friction or scrollFriction local listener = options.listener local bgColor = options.bgColor or {} bgColor[1] = bgColor[1] or 255 bgColor[2] = bgColor[2] or bgColor[1] bgColor[3] = bgColor[3] or bgColor[1] bgColor[4] = bgColor[4] or 0 print("REMEMBER: THE SCROLLVIEW IS INVISIBLE") local maskFile = options.maskFile local hideBackground = options.hideBackground local isVirtualized = options.isVirtualized local topPadding = options.topPadding local bottomPadding = options.bottomPadding local baseDir = options.baseDir or system.ResourceDirectory

 function buildTabBar() if imageIndex[49] ~= nil then imageIndex[49]:removeSelf() imageIndex[49] = nil end local toolbarGradient = graphics.newGradient( {236, 237, 240}, {139, 157, 180}, "down" ) local tabBar = widget.newTabBar{ top = 0, width = display.contentWidth, height = 90, left = 0, gradient = toolbarGradient, } return tabBar; end

Hi @MatthewCharlesHarrop,

Are all of the issues related to the legacy widgets library? Or is it more general? Is there a specific reason why you’re using the legacy widgets versus the current widgets?

Thanks,

Brent

After more digging, it appears that the problems only relate to the graphics library.

Deploying updates and upgrades to our privately deployed base of customers would be very difficult because they run on a 12 month development cycle.

Hi Matthew,

I’m not sure if I understand… you can’t implement the current widget library for which reasons?

Brent

Hi @MatthewCharlesHarrop,

Are all of the issues related to the legacy widgets library? Or is it more general? Is there a specific reason why you’re using the legacy widgets versus the current widgets?

Thanks,

Brent

After more digging, it appears that the problems only relate to the graphics library.

Deploying updates and upgrades to our privately deployed base of customers would be very difficult because they run on a 12 month development cycle.

Hi Matthew,

I’m not sure if I understand… you can’t implement the current widget library for which reasons?

Brent