Can't get widgets to function properly, and another simple question...

I’ve been working on getting 2 widgets to function correctly for about the past 9 hours!  If anyone is wondering, yes I have the new public release installed.

Problem 1:  My tab bar only works when it is docked to the left side of the screen, but I don’t want it there. When I change the left and top values, they no longer work when clicked. Lo and behold, when I change the left value back to 0, they work again!

Problem 2:  I cannot get the widget themes to work.  I am trying to incorporate a picker wheel, but am unable to set the theme.  I have read the API library… I am more of a visual learner. :\  I have searched the forums and the web, can’t find any answers that have helped me.  I have even tried incorporating the widget library from github in order to make sure that I had the correct lua file when setting   widget.setTheme( “widget_theme_ios” ) .

I have now taken all of those widget files out, since they didn’t seem to help me.  Here is my resulting code (where the tab bar buttons will not click and the picker wheel is all plain and bare!):

local widget = require ("widget") widget.setTheme = ("widget\_theme\_ios") local tabButtons = { { width = 30, height = 30, defaultFile = "buttons/mybuttonclicked.png", overFile = "buttons/mybutton.png", label = "Boy", labelColor = { default = {139, 0, 139}, over = { 238 ,201, 0 }, }, font = native.systemFontBold, size = 20, onPress = function (event) boyC.isVisible = true; girlC.isVisible = false; end, selected = true }, { width = 30, height = 30, defaultFile = "buttons/mybuttonclicked.png", overFile = "buttons/mybutton.png", label = "Girl", labelColor = { default = {139, 0, 139 }, over = { 238 ,201, 0 }, }, font = native.systemFontBold, size = 20, onPress = function (event) boyC.isVisible = false; girlC.isVisible = true; end, selected = false } } -- tab bar for gender change buttons local tabBar = widget.newTabBar { left =screenRight - 300, top = screenTop + 50, width= 80, height = 80, buttons = tabButtons } group:insert( tabBar ) --picker wheel for birth date local days = {} for i = 1, 31 do days[i] = i end -- Set up the Picker Wheel's columns local columnData = { { align = "left", width = 100, startIndex = 1, labels = { "January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November", "December" }, }, { align = "right", width = 40, startIndex = 1, labels = days, } } -- Create a new Picker Wheel local pickerWheel = widget.newPickerWheel { left = screenRight - 200, top = screenTop + 130, font = native.systemFontBold, columns = columnData, } group:insert(pickerWheel)

Thank you if you actually went over all of that! :slight_smile:  Now, for my question:

I thought the way rgb color values worked was different now, but they still seem to be working for me fine. Did that only change for paid subscribers?

Any help or support of any kind is much appreciated!  

Hi @monifin,

I’ve confirmed this bug (non left=0 positioning) and reported it to the engineers. We’ll investigate a.s.a.p.

As for the RGB values, are you using V1 Compatibility mode? If not, you should convert to the new 1-based values (or just put a “/255” after your current values, like:

[lua]( 255/255, 150/255, 168/255 )

[/lua]

Best regards,

Brent

I’ve been working on getting 2 widgets to function correctly for about the past 9 hours!  If anyone is wondering, yes I have the new public release installed.

10x faster to develop with eh…  :frowning:

Thanks Brent.  I did see another topic talking about the left positioning being a bug, but it didn’t make sense to me that it did work if it was positioned at that 0 point, so I kept trying- thinking maybe I was crazy!

@ksan- Seeing as how I’m a beginner and have absolutely no previous coding experience, I am really enjoying working with Corona.  The struggle was that I was trying to work on something that was bugged because I thought maybe it was my own deficiency.  I’m sure once I have a more firm grasp on the lua language, the APIs, and my own ability… it will definitely go a lot faster! :slight_smile:  

@ monifin, I am sorry if I sounded as though I was looking down on your work. Wasn’t at all the intention. I was poking a little jab at Corona Labs 10x faster to develop with promise for their product. These bugs have been slowing us further and further of late… 

As before, we are aware of these and will roll in fixes as soon as we can. Kerem, I’d also like to touch base with you next week sometime to figure out exactly which issues are open (and which resolved) in Build #2076.

Have a good weekend,

Brent

Thanks Brent. Have a good weekend. Talk to you next week. 

Hi @monifin,

I’ve confirmed this bug (non left=0 positioning) and reported it to the engineers. We’ll investigate a.s.a.p.

As for the RGB values, are you using V1 Compatibility mode? If not, you should convert to the new 1-based values (or just put a “/255” after your current values, like:

[lua]( 255/255, 150/255, 168/255 )

[/lua]

Best regards,

Brent

I’ve been working on getting 2 widgets to function correctly for about the past 9 hours!  If anyone is wondering, yes I have the new public release installed.

10x faster to develop with eh…  :frowning:

Thanks Brent.  I did see another topic talking about the left positioning being a bug, but it didn’t make sense to me that it did work if it was positioned at that 0 point, so I kept trying- thinking maybe I was crazy!

@ksan- Seeing as how I’m a beginner and have absolutely no previous coding experience, I am really enjoying working with Corona.  The struggle was that I was trying to work on something that was bugged because I thought maybe it was my own deficiency.  I’m sure once I have a more firm grasp on the lua language, the APIs, and my own ability… it will definitely go a lot faster! :slight_smile:  

@ monifin, I am sorry if I sounded as though I was looking down on your work. Wasn’t at all the intention. I was poking a little jab at Corona Labs 10x faster to develop with promise for their product. These bugs have been slowing us further and further of late… 

As before, we are aware of these and will roll in fixes as soon as we can. Kerem, I’d also like to touch base with you next week sometime to figure out exactly which issues are open (and which resolved) in Build #2076.

Have a good weekend,

Brent

Thanks Brent. Have a good weekend. Talk to you next week.