Button Widget broken in new daily build

Solar2D Daily Builds and Public Releases
1

The button widget seems not to work correctly when setting the left and the top values, my buttons were all aligned correctly and then the update pushed them all left.

If you don’t set left and top and set x and y, it seems to ignore the anchor values, so for instance if I set anchorX =0.0 for my button and set the position x=0 then you’d expect the button to be placed on the left edge of the screen, instead it puts the center point of the button at 0 and appears half off and half on. This was working before the recent changes. 

2

Hi @cublah,

Can you please post some sample code where you’re doing this so I can test and confirm?

Thanks,

Brent

3

Yeah, I’m seeing a similar thing with the latest Daily Build 2585.

The button should be at the same position and size as this rectangle:

image = display.newRect ( 234, 1348, 102, 44 )

But instead it appears at the correct Y but pushed along on the X by around 100 odd?

Also with stroke at zero, the resulting button is smaller by a pixel or 3 than the newRect created with the same parameters.

 local widget = require( "widget" ) -- Create the widget local button1 = widget.newButton { label = "button", emboss = false, width = 102, height = 44, fillColor = { default={ unpack(black) }, over={ 1, 0.1, 0.7, 0.4 } }, strokeColor = { default={ 1, 0.4, 0, 1 }, over={ 0.8, 0.8, 1, 1 } }, strokeWidth = 0 } -- Center the button button1.x = 234 button1.y = 1348
4

Hi @kilopop,

Did this button alignment thing just begin to happen in recent daily builds, or has it been this way for awhile?

As for the stroke, I don’t suggest setting it to 0. Just don’t specify that parameter at all if you don’t want a stroke on the button.

Brent

5

This is the first time I’ve used the button widget in many a version. So I can only speak for the latest build.

Also, the size of the button changes between different device sizes on the simulator (mac and windows). So the size difference is not due to the stroke as I originally thought as it is still smaller when that parameter is removed.

This is my config.lua if that is relevant:

local kScale = "letterbox" if ( string.sub( system.getInfo("model"), 1, 4 ) == "iPad" ) then -- all iPads checking application = { content = { width = 1536, height = 2048, fps = 60, scale = kScale, imageSuffix = { ["@2"] = .5, ["@4"] = .2, } }, } elseif ( display.pixelHeight \> 1024 ) then -- iPhone 5 (and all other high-res devices) checking - uses the New iPad Retina image application = { content = { width = 1536, height = 2048, fps = 60, scale = kScale, }, } else -- all other devices application = { content = { width = 1536, height = 2048, fps = 60, scale = kScale, imageSuffix = { ["@2"] = .5, ["@4"] = .2, } }, } end
6

I’m also getting runtime errors on button touch when adding a strokeWidth. Tried filing a bug report but I didnt get a confirmation so I don’t know if it was received.

7

Hi @zv713,

Can you please post your code? In the future, we appreciate if you attempt to get help in the forums before you file a bug report. It might be one tiny issue with your code, and not a bug in the SDK.

Thanks,

Brent

8

[lua]

local widget = require(“widget”)

local tile = widget.newButton ( {

    x=display.contentCenterX,

    y=display.contentCenterY,

    shape=“rect”,

    height=44,

    width=44,

    fillColor = { default={ 1, 1, 1, 1 }, over={ 0.9, 0.9, 0.9, 1 } },

    strokeColor = { default={ 0.3, 0.6, 0.8, 1 } },

    strokeWidth = 1

    })

[/lua]

commenting out the strokeWidth line fixes the error

9

Hi @zv713,

It appears that you omitted the “over” color table for the stroke. I believe both are required if you use the “strokeColor” parameter. Please add that and see if the error stops.

Brent

10

That did the job. Thanks for the quick reply.

11

Happy to help. If you receive a confirmation on the bug case you filed, can you please post the # here? I would like to close that case since it’s not a bug.

Thanks,

Brent

12

No confirmation on my end as of yet, and I recall having trouble getting my bug reports received back in August. Not sure if there was something wrong with my account, or the form, and whether this was sorted out since then.

Will message if I get anything.

13

ok it seems that it’s because my down state button is trimmed in my sprite sheet, but surely that shouldn’t matter, it did work before

14

I had to add “labelAlign = left” to get it to behave and honor anchorX = 0

update: no, that didn’t work either

I have 

backgroundText = display.newText(“background”, left, top, native.systemFont, 16)

backgroundText.anchorX = 0

dialogGroup:insert(backgroundText)

clearButton = widget.newButton({label = “clear”, labelAlign = “left”, left = left, top = top + 10})

clearButton.anchorX = 0

dialogGroup:insert(clearButton)

I get the results shown in the attached file.  I expected the 2 items to be left aligned.

15

This works

clearButton = widget.newButton({label = “clear”, labelAlign = “left”})

clearButton.anchorX = 0

clearButton.x = left

clearButton.y = top + 10

16

Hi @cublah,

Can you please post some sample code where you’re doing this so I can test and confirm?

Thanks,

Brent

17

Yeah, I’m seeing a similar thing with the latest Daily Build 2585.

The button should be at the same position and size as this rectangle:

image = display.newRect ( 234, 1348, 102, 44 )

But instead it appears at the correct Y but pushed along on the X by around 100 odd?

Also with stroke at zero, the resulting button is smaller by a pixel or 3 than the newRect created with the same parameters.

 local widget = require( "widget" ) -- Create the widget local button1 = widget.newButton { label = "button", emboss = false, width = 102, height = 44, fillColor = { default={ unpack(black) }, over={ 1, 0.1, 0.7, 0.4 } }, strokeColor = { default={ 1, 0.4, 0, 1 }, over={ 0.8, 0.8, 1, 1 } }, strokeWidth = 0 } -- Center the button button1.x = 234 button1.y = 1348
18

Hi @kilopop,

Did this button alignment thing just begin to happen in recent daily builds, or has it been this way for awhile?

As for the stroke, I don’t suggest setting it to 0. Just don’t specify that parameter at all if you don’t want a stroke on the button.

Brent

19

This is the first time I’ve used the button widget in many a version. So I can only speak for the latest build.

Also, the size of the button changes between different device sizes on the simulator (mac and windows). So the size difference is not due to the stroke as I originally thought as it is still smaller when that parameter is removed.

This is my config.lua if that is relevant:

local kScale = "letterbox" if ( string.sub( system.getInfo("model"), 1, 4 ) == "iPad" ) then -- all iPads checking application = { content = { width = 1536, height = 2048, fps = 60, scale = kScale, imageSuffix = { ["@2"] = .5, ["@4"] = .2, } }, } elseif ( display.pixelHeight \> 1024 ) then -- iPhone 5 (and all other high-res devices) checking - uses the New iPad Retina image application = { content = { width = 1536, height = 2048, fps = 60, scale = kScale, }, } else -- all other devices application = { content = { width = 1536, height = 2048, fps = 60, scale = kScale, imageSuffix = { ["@2"] = .5, ["@4"] = .2, } }, } end
20

I’m also getting runtime errors on button touch when adding a strokeWidth. Tried filing a bug report but I didnt get a confirmation so I don’t know if it was received.