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

Solar2D Widgets
#1

Fellow Corona SDK users, 

On July 10 2013 Walter said the following in response to a question from me… 

We’ve fixed all the top ones on our list for widget and have been turning our attention to non-widget ones like Facebook.

Just looking at this forum and seeing all the issues we are still facing, I beg to differ.

I think a lot of widget issues still remain at large and need continued focus and attention. I asked Walter if he would be ok to open up the bug reporting system so we could see a neat report of open bugs to which I received no response which is not surprising.

So here is an idea. Lets compile our own list!!! A short and simple list. I started it by going through the forum and capturing few bugs that stood out. It would be wonderful if you could simply click on the link below and update the Google Docs spreadsheet with your bug(s) that you are still waiting on. 

Corona SDK Widget 2.0 Bugs

I truly believe Walter is wrong (no offense) in thinking that the top issues in Widget 2.0 have been addressed and I feel the only way to rally the troops is through dialogue and transparency. Lets work together to build this simple list which we can refer to. 

Walter, Alex, Brent et al, please don’t take this the wrong way. I’m not a troll nor am I trying to hurt Corona Labs. I have utmost respect for the work you are doing. I simply want you to succeed because building on your success we can build bigger monuments to showcase Corona SDK and its capabilities.

Please allocate the resources that widget 2.0 needs in order to become reliable, bug free and robust so we can move forward and not backwards all the time. 

Thanks much for all your continued efforts. 

EDIT : Alex says : for forum threads that have no bug reports, please provide the exact link to the thread. Thanks.

EDIT 2 : The spreadsheet is growing and a number of items that are fixed make it hard to see what is still out there. I will create a second sheet for fixed items and move confirmed fixes there. 

#2

I reported a tableView bug about deleting rows on June 30th, number 1153.

I consider the bug quite bad, table view behaves very erratically after deleting a row. I can not publish without this being fixed. Not that I plan on publishing in the next few weeks so I’m not too stressed (until I saw that comment from Walter).

After deleting a row and tapping anywhere on table view things start jumping around. Also deleting more than 1 row they animate incorrectly.

Made a video: http://www.youtube.com/watch?v=VbwdjMmLrJI

Each time the tableview moves up or down I’m just tapping on the tableview (no dragging).

This is build 1153, but bug was also in at least previous 2 daily before that. I haven’t tried more than that.

Minimum code to reproduce:

[lua]

display.setStatusBar( display.HiddenStatusBar )

local widget = require( “widget” )

local tableView

local function onRowTouch( event )

    local rowNumber = event.target.index

    if event.phase == ‘tap’ then

        tableView:deleteRow(rowNumber)

    end

end

local function onRowRender( event )

    local row = event.row

    local rowTitle = display.newText( row, "DELETE ME " … row.index, 0, 0, nil, 14 )

    rowTitle.x = display.contentWidth / 2

    rowTitle.y = row.contentHeight * 0.5

    rowTitle:setTextColor( 0, 0, 0 )

end

– Create a tableView

tableView = widget.newTableView

{

    width = display.contentWidth, 

    height = display.contentHeight,

    onRowRender = onRowRender,

    onRowTouch = onRowTouch,

}

tableView:insertRow{rowHeight = 40}

tableView:insertRow{rowHeight = 40}

tableView:insertRow{rowHeight = 40}

[/lua]

#3

Jon, thanks much for your contribution. Most appreciated. 

#4

Kerem,

Letting you know that some of the bugs in the document are already in the works, and that i’m watching the thread closely.

I think it’s a great idea to have this centralized.

Alex

#5

@jonjonnson: The fix for the tableview delete row problems will be available very soon.

Alex

#6

Hi Alex, 

Thanks for your kind words and participation in this thread. Most appreciated. I am sure we all look forward to your updates on a daily basis!!! Keep up the great work.

Regards,

Kerem

#7

Great, thanks Alex.

#8

This is not a bug, but I’d like to see more frequent releases of the code. It doesn’t look like GitHub even has the changes from the last public build.

#9

I would like to finally see the widgets UI customization documentation, examples, and tutorial we were promised.

#10

Hi Chevol,

Better late than never… Part 1 at least.

http://www.coronalabs.com/blog/2013/07/16/tutorial-stylizing-widgets-part-1/

This was underway before you posted; it might not cover the specific widget you need to style (in this first part), but this should provide some clearer “real world” examples.

Take care,

Brent

#11

+1 for Chevol’s suggestion. Brent thanks much for the tutorial. Its great that these are coming out!!! Thank you .

#12

Great thread and idea. Added my outstanding bugs and a column so it’s clear what widgets we’re talking about :slight_smile:

#13

Richard, thanks much for your contribution. Great idea to add the widgetName in a column. It does make it much clearer indeed. 

On a related note, if anyone’s bug is fixed please remember to come and add the Closed Date. 

All contributions are most appreciated. I will make one more pass through the forum and try to catch some more but its best if the person who first reported a bug follows through with it in the spreadsheet as well.

Regards,

Kerem

#14

Alex, the latest daily is amazing!!! Widget fixes galore. Thank you very very much! Have a wonderful weekend and well deserved weekend. All the best!!!

#15

Thanks much to those of you who are registering their bugs and/or updating the existing bugs with status after recent fixes by Alex. May I suggest that once a bug is confirmed fixed you simply note the fact that its fixed in the notes or remarks column and hide that row in the spreadsheet? This way we can keep the active in our attention. Thank you very much!!!

#16

ksan, highly recommend you stop deleting entries; would make more sense to grey them out or move them to a second sheet. Else could be confusing for people looking into bug status

#17

Hi Richard, I would never delete entries from a list like this. As I mentioned in my post right above yours I was contemplating hiding the rows for resolved / fixed bugs but I can see this will cause confusion. I think your idea is a better one to gray them out and move them to the end of the list etc. I will do that from now on. Thanks much for your suggestion.

#18

Ah I didn’t look at the doc history. Just saw a solved bug was deleted from the sheet.

#19

Anyone else experiencing a bug with tableview categories?

When scrolling a tableview up the top category changes to match the contents of the last row in the tableview. With so many changes to widgets I am not sure at this point if it’s a bug or me. 

#20

It seems to work well for me. I’m not observing the bug you mention. Suggest you try changing WidgetDemo in your side and see if you can duplicate the issue.