Widget 2.0: Row Background And Line Rendering

Solar2D Widgets
#1

Danny,

Have seen this one for weeks and am now convinced it is in the Widget code.

Using build 1074 currently.

Take a look at the image attached

 (Rant:  let me take one more opportunity to complain about the attachment limit on these tickets.  How can we give you visual evidence about issues with a 14.32K limit … that is way too small please poke someone on this issue) …

anyway …

the top portion of the image is how it renders the first time into the scene … all is well … however, sometimes when i have called deleteAllRows and reinserted all the content i get the second image where the row lines are missing and the background highlight is shifted to the left.  

I see this on all my table views that call removeAllRows … always shifted about the same amount to the left and the row lines missing.  All our tableViews use masks to limit their vertical extent.

Other than this background and row line issue our table views are functioning properly.

This is rather a large issue for us.  Please to take a look at this … see if there may be something in the widget code that would be causing this issue.

#2

Danny,

Have seen this one for weeks and am now convinced it is in the Widget code.

Using build 1074 currently.

Take a look at the image attached

 (Rant:  let me take one more opportunity to complain about the attachment limit on these tickets.  How can we give you visual evidence about issues with a 14.32K limit … that is way too small please poke someone on this issue) …

anyway …

the top portion of the image is how it renders the first time into the scene … all is well … however, sometimes when i have called deleteAllRows and reinserted all the content i get the second image where the row lines are missing and the background highlight is shifted to the left.  

I see this on all my table views that call removeAllRows … always shifted about the same amount to the left and the row lines missing.  All our tableViews use masks to limit their vertical extent.

Other than this background and row line issue our table views are functioning properly.

This is rather a large issue for us.  Please to take a look at this … see if there may be something in the widget code that would be causing this issue.

Hey.

I have asked the team about increasing the limit on attachments.

Now onto your issue. Is this with the latest public release (1076 ) ?

If so would you please [buglink] with a simple reproducible test case and I will validate this and add it to my queue.

Thanks

#3

I too see this EXACT same issue. Have you submitted a bug yet?

#4

Have not had time too … if u have a reproducer I would be much abliged if you could submit

#5

I don’t have time to build you a reproducer for this one … however, given that i am not the only one to see this i would suggest that it is in fact a bug.  One piece of info that may be related, it seems that the use of Overlays may be involved in creating this problem for me.

Im my case, my scene with the table View exists, I move to the next scene on that scene i generate an overlay action, dismiss the overlay putting me back in my second scene, going back to my first scene from there (back to the one with the table view) seems to generate the issues every time. 

It is like your code gets confused as to where the boundaries of the scene are.

It does not seem to be related to the scene transitions as removing the transitions does not cause the issue to go away.

Really seems to have to do with asking for the overlay.

Real issue … just don’t have time to debug this one currently anymore.  Please take a look.

#6

Noticed something additional on this issue today.  On some rows when the background is shifted off to the left … unless i touch on an element i put in the row or on part of the visible background the touch event is not firing.  Taping a blank area where there is no background (due to the shift left) no touch event is occuring.

This is a VERY big issue.  I simply do not have the time to write a test case for this.

#7

This situation occurs when the row is shifted off to the left ie your first post right?

#8

Yea … some times it is shifted as much as 75% to the left. … Seems to always be to the left 

Note that the lines always seem to be missing when this occurs

#9

ps … using 1076

#10

Understood. So the steps to reproduce are basically:

  1. Create a tableView

  2. At some stage call deleteAllRows()

  3. Re-create the tableView (content gets shifted to the left)

?

#11

Well not quite … i think as i mentioned that it may have something to do with overlays being in the mix.

Im my case, my scene with the table View exists, I move to the next scene. In the second scene i generate an overlay action, dismiss the overlay putting me back in my second scene. Now going back to my first scene from there (back to the one with the table view) seems to generate the issues every time.   Note that when i return to that first scene i am calling deleteAllRows to rerender the table from the DB.

Simply going from my first scene to second scene and back (forcing the call to deleteAllRows) does not cause the issue. Only when i hit the overlay in that second scene.

I know it makes no sense but somehow what is happening is confusing the Highlight code for the table view.

Almost like it is computing the left boundary badly.

I did notice that the row.width would sometimes get confused so i had to go with screenWidth and could not rely on row.width that would come up short some times.  … have not tested that in a while so do not know if that is also an issue on 1076.

#12

Got it. I will investigate

#13

Hi.

First time the newTableView displays correctly.

I then display a Pickerwheel on screen, make a choice and transition it out (I do not remove it). Based on the choice I remove all rows from the list (NewTableView) and perform a rebuild.

After that the width of the rows of the NewTableView is limited to the width of the newPickerWheel (150 in this case). Also the lines between the rows have disappeared.

One solution is to remove the list and create it again.

Another solution is to create a dummy newPickerWheel with a width of 320 and remove that again before refilling the list. This does NOT solve the problem of the lines that have disappeared.

I am using build: 

Copyright © 2009-2013  C o r o n a   L a b s   I n c .

        Version: 2.0.0

        Build: 2013.1076

Below the code of the newTableView and the newPickerWheel I used.

list = widget.newTableView{

      width = 320, 

      height = 366,

      bottomPadding = 20,

      maskFile = “assets/mask-320x366.png”,

      hideBackground = true,

      onRowRender = onrowRender,

      onRowTouch = onrowTouch,

      noLines = false

   }

   list.y = 108

   list.x = 0

columnData[1].align = “center”

columnData[1].width = 150

columnData[1].labels = content{}

picker = widget.newPickerWheel{

     top = 550,

    font = native.systemFontBold,

     columns = columnData,

 }

#14

This sounds similar to the issue i see but my picker wheel is the full width of the screen as is my tableView and i see this issue.  I also notice that the amount of shifting to the left is not the same every time.

Danny … any luck with this … had some people beta testing and they ran into trouble with the app due to this problem.

Cheers

#15

Danny,

Have seen this one for weeks and am now convinced it is in the Widget code.

Using build 1074 currently.

Take a look at the image attached

 (Rant:  let me take one more opportunity to complain about the attachment limit on these tickets.  How can we give you visual evidence about issues with a 14.32K limit … that is way too small please poke someone on this issue) …

anyway …

the top portion of the image is how it renders the first time into the scene … all is well … however, sometimes when i have called deleteAllRows and reinserted all the content i get the second image where the row lines are missing and the background highlight is shifted to the left.  

I see this on all my table views that call removeAllRows … always shifted about the same amount to the left and the row lines missing.  All our tableViews use masks to limit their vertical extent.

Other than this background and row line issue our table views are functioning properly.

This is rather a large issue for us.  Please to take a look at this … see if there may be something in the widget code that would be causing this issue.

Hey.

I have asked the team about increasing the limit on attachments.

Now onto your issue. Is this with the latest public release (1076 ) ?

If so would you please [buglink] with a simple reproducible test case and I will validate this and add it to my queue.

Thanks

#16

I too see this EXACT same issue. Have you submitted a bug yet?

#17

Have not had time too … if u have a reproducer I would be much abliged if you could submit

#18

Work around is to create a dummy newTableView and remove it right away. The settings of that newTableView will hold for the original newTableView, including lines and width. Strange but true.

Another issue is that the last setting of noLines will override any settings of previous newTableViews. So if the last newTableView you defined is one with noLines = true, all previous newTableViews you defined will have that same property. Here again, creating and removing the dummy tableview is the work around. Actually that is the way I discovered the work around  :stuck_out_tongue:

Perhaps you can use this work around.

I am still using 1076. Don’t dare to go forward at the moment.

#19

I don’t have time to build you a reproducer for this one … however, given that i am not the only one to see this i would suggest that it is in fact a bug.  One piece of info that may be related, it seems that the use of Overlays may be involved in creating this problem for me.

Im my case, my scene with the table View exists, I move to the next scene on that scene i generate an overlay action, dismiss the overlay putting me back in my second scene, going back to my first scene from there (back to the one with the table view) seems to generate the issues every time. 

It is like your code gets confused as to where the boundaries of the scene are.

It does not seem to be related to the scene transitions as removing the transitions does not cause the issue to go away.

Really seems to have to do with asking for the overlay.

Real issue … just don’t have time to debug this one currently anymore.  Please take a look.

#20

Noticed something additional on this issue today.  On some rows when the background is shifted off to the left … unless i touch on an element i put in the row or on part of the visible background the touch event is not firing.  Taping a blank area where there is no background (due to the shift left) no touch event is occuring.

This is a VERY big issue.  I simply do not have the time to write a test case for this.