Bug in Tab Bar widget with G2?

Solar2D Advanced Graphics
#1

It looks like there is a bug in the tab bar widget with graphics 2.0

If someone has a minute, can they confirm that if a “left” is set in the setup, that it screws up all the touches (i.e. all the touch areas don’t seem to move with the visual tab bar). You tap on tab1 and tab2 is selected etc

Dropping this into the TabBar demo project seems to break it:

local demoTabs = widget.newTabBar

{

    left = 50,

    top = display.contentHeight - 50,

    width = display.contentWidth,

    backgroundFile = “assets/tabbar.png”,

    tabSelectedLeftFile = “assets/tabBar_tabSelectedLeft.png”,

    tabSelectedMiddleFile = “assets/tabBar_tabSelectedMiddle.png”,

    tabSelectedRightFile = “assets/tabBar_tabSelectedRight.png”,

    tabSelectedFrameWidth = 20,

    tabSelectedFrameHeight = 52,

    buttons = tabButtons

}

Thanks,

David

#2

Hi @playthisstudios,

Can you pinpoint a specific G2.0 build for this?

Thanks,

Brent

#3

Hi Brent,

Currently running 2045

#4

OK, thanks. We have fixed several little widget visual things since then and will roll them out as soon as we can. They should fix the issue you’re seeing.

Brent

#5

Thanks for the quick reply Brent, so will that fix be in the next build after 2063 (current)?

#6

Yes, this should be… please test in tomorrow’s daily and let me know if the issue is not resolved. :slight_smile:

#7

Will do! Thanks Brent

#8

Hey Brent, just grabbed 2064 that was just put up and this problem still occurs.

Thx

David

#9

This appears to be a bug.  Can we get you to file a bug report using the “Report a bug” link at the top of the page, so we can get this in engineering’s queue.

Thanks

Rob

#10

Thanks Rob, bug submitted.

Dave

#11

Hi @playthisstudios,

Can you pinpoint a specific G2.0 build for this?

Thanks,

Brent

#12

Hi Brent,

Currently running 2045

#13

OK, thanks. We have fixed several little widget visual things since then and will roll them out as soon as we can. They should fix the issue you’re seeing.

Brent

#14

Thanks for the quick reply Brent, so will that fix be in the next build after 2063 (current)?

#15

Yes, this should be… please test in tomorrow’s daily and let me know if the issue is not resolved. :slight_smile:

#16

Will do! Thanks Brent

#17

Hey Brent, just grabbed 2064 that was just put up and this problem still occurs.

Thx

David

#18

This appears to be a bug.  Can we get you to file a bug report using the “Report a bug” link at the top of the page, so we can get this in engineering’s queue.

Thanks

Rob

#19

Thanks Rob, bug submitted.

Dave