Widget 2.0 tabBar Troubles

Solar2D Widgets
#21

I’m still cannot get this to work without an error. I started with a clean slate just to work on the tabBar. Below is the tabBar code and then the error messages after that. I only used “required” commands or whatever…
 

local widget = require( "widget" ) local tabButtons = { { width = 50, height = 51, defaultFile = "tabHome.png", overFile = "tabHomeD.png", }, { width = 50, height = 51, defaultFile = "tabFavorites.png", overFile = "tabFavoritesD.png", } } local tabBar = widget.newTabBar { height = 70, buttons = tabButtons, backgroundFile = "leather.png", tabSelectedLeftFile = "slider-fill.png", tabSelectedMiddleFile = "slider-fill.png", tabSelectedRightFile = "slider-fill.png", tabSelectedFrameWidth = 60, tabSelectedFrameWidth = 60, }

----------- 
ERROR: bad argument #5 to display.newImageRect(): height expected, but got number.
ERROR: bad argument #5 to display.newImageRect(): height expected, but got number.
ERROR: bad argument #5 to display.newImageRect(): height expected, but got number.
Runtime error
bad argument #2 to ‘newText’ (string expected, got nil)
stack traceback:
[C]: ?
[C]: in function ‘newText’
?: in function ‘?’
?: in function <?:580>
(tail call): ?
…53qq7ztjxw2q5kcnh0000gn/T/TemporaryItems/24/main.lua:34: in main chunk

 
I’m sorry for all the trouble, but I’m no pro at this and I can go no farther unless this is solved.

#22

The one error makes it look like the label field is required (the only string I can see it using).  Try passing a label to the button.  If you don’t want the label just make it a space.  Also the three errors:

ERROR: bad argument #5 to display.newImageRect(): height expected, but got number.

is due to you missing a required:

tabSelectedFrameHeight = 60,

You repeated …FrameWidth twice.

#23

Thanks!

I fixed those two things and it performed smoothly! However, applying a label shifts the button off center (and I don’t want labels). Playing with the x and y offsets didn’t change anything. I can continue to work on other thing now that the tabBar is performing properly (almost), but I will need this fixed eventually.