List of open Widget 2.0 bugs & promised features...

Solar2D Widgets
#441

Hey alex,

excellent news. thanks. Really need this fixes till mid / end next week.  I will try to fill a bug report for you.

#442

@searchm: Thanks, that would be great because i can run it through the codebase and see if your issue gets fixed.

alex

#443

@alexf

okay I’ve filled out a bug report called tableView 2.0 bugs.

Thanks! Most appreciated.

#444

@searchm: received. Thanks!!!

alex

#445

You’re welcome. Can’t wait to use rock solid widgets soon.

I also mentioned in the bug report that the isLocked feature doesn’t work.

regarding the scrollView widget:

beside the sloppy scroll behaviour in scrollView there’s also another tiny bug, which maybe also affects the tableView ( I’m not sure ):

Video:

Scroll to the bottom a little slower and the scrollbar will sometimes go beyond the limit. If the scrollView height is smaller then the display height it will not respect the limits. It will jump to where it belongs when the scrolling is done though.

https://vimeo.com/89618405

#446

and please implement a onClose, onChange Listener :slight_smile:

#447

Hey guys,

2014.2183 fixes:

#26439: widget.setTheme widget_theme_ios7 issue with tableView
#28359: tableView row.height and row.contentHeight is reported wrongly in ORR
#29678: tableView structure is misaligned
#29905: Tableview with row width inconsistent
#27439: tableview with params & iscategory
#29142: widget.newStepper:setValue does not update newStepper.value (the stepper now has a getValue() method)
#30229: widget.newPickerView not releasing all memory.
#25855: ButtonWidget causes texture memory leak

More on the way.

Thanks,

alex

#448

Awesome thanks a lot Alex!

#449

Alex , the list is awesome! Thanks for putting in the effort in fixing the bugs and open communications here. 

Corona Labs leadership , David, Walter, thanks for hearing our calls and allowing this to happen. One more day to the anniversary and I do think we have gained significant momentum. I hope this becomes the norm rather than the exception. Thank you very much!!!

Bug owners in the spreadsheet… Please verify your bugs and move them to the fixed tab if all looks ok. Thanks much!!!

#450

Thanks for the update, but there are still some major issues which are not easy to describe as a bug report, so I made a little video again.

http://www.youtube.com/watch?v=KJjo_0hSoSA&feature=youtu.be

  1. Tableview doesn’t scroll back if finger moved more in x direction as in y, which I posted already.

  2. Rows don’t move correct back, what produces a gap between the rows

  3. Tableview position not correct by switching back from outside the screen after deleting a row

Before the update I could avoid the issues by reload the tableview after deletions, but there is now a incorrect row position anyway. 

I also reported a bug with samplecode. The number is 30735.

Thanks!

edit:

  1. a tableView:reloadData() call after a deletion causes that the row above and under the deleted row are too close together. The line of the last pixel of the upper row is covered from the lower row then. I have a shadow line as the last line of my row background, so this is very annoying.  
#451

Skatan - I had the same problems as you… it was driving me nuts.  I think I traced it down to the default anchor’s.  I set the default anchorX/Y=0.    If I set the default anchor to 

      display.setDefault( “anchorX”, .5 )

      display.setDefault( “anchorY”, .5 )

before creating my newPickerWheel and then setting back to 0 after it is created the problem appears to be fixed.

Looks like the newWheelpicker only plays nice with the default anchor point set to 0.5.

#452

I have the same bug like @Sunmils.

I need quick fixing please.

#453

In the works.

alex

#454

Alex -

Any idea when the next free build with some of these fixes will be available?  You fixed a bug I opened a couple months ago, yet the free download is still at rev from mid-Dec: 

Build 2013.2100

Sorry, I realize this is slightly off topic, just really frustrated as the last build is almost 4 months old now…

#455

We are working to finalize the next public build now.  We are trying to squeeze in a couple of last fixes, make sure we didn’t break anything that was working in 2100.  I can’t give you a date, other than soon.

Rob

#456

@Rob,Alex

Please update the github repository once the public build is finalized.

Thank you.

#457

as primoz.cerar mentioned ^

#458

I have some long requested fixes in the 2189 fix list. Yet to test them but this is great news! Thanks for rolling out these bug fixes. Much appreciated. 

#459

@ksan: You’re welcome.

@eja, primoz.cerar: It will be done.

alex

#460

The scrollview has improved a bit in 2014.2189.

But sometimes the scrollview content jumps when I start scrolling down. Like it’s magnetically snapped to the top, moves a bit, jumps back to zero and then makes a big jump and suddenly scrolls. It’s the same vice versa from the bottom.

It’s not as fluid as it was half a year ago. Overall the usability got worse.

Please fix this quickly.