I have submitted a bug report for this as well, strange things happening when deleting single rows, adding rows and deleting all rows. Hopefully this gets a fix soon.
Was this ever resolved? I’m working with ver.1137 and am getting similar errors to that which others have reported. In the attached case, I remove row 3 one second into app launch and the rows adjust. When the table is scrolled afterward, however, a large gap appears between rows 2 and 4 if those respective rows disappear from view and between rows 12 and 13 (or others) if those rows disappear from view.
A Gist of the main.lua file: https://gist.github.com/cheetomoskeeto/5951633
A screencast of the problem: https://www.dropbox.com/s/1w98tzziyaq9enb/tableView-wierdness-20130708.mp4
Was this ever resolved? I’m working with ver.1137 and am getting similar errors to that which others have reported. In the attached case, I remove row 3 one second into app launch and the rows adjust. When the table is scrolled afterward, however, a large gap appears between rows 2 and 4 if those respective rows disappear from view and between rows 12 and 13 (or others) if those rows disappear from view.
A Gist of the main.lua file: https://gist.github.com/cheetomoskeeto/5951633
A screencast of the problem: https://www.dropbox.com/s/1w98tzziyaq9enb/tableView-wierdness-20130708.mp4
I’m seeing the “A row cannot be deleted whilst the tableView is scrolling” warning in build 1217. It doesn’t happen every time – but every time it happens the list is NOT scrolling.
Anybody have a fix or workaround?
I’m using the internal widget library, not the github version.
Jay
I’m seeing the “A row cannot be deleted whilst the tableView is scrolling” warning in build 1217. It doesn’t happen every time – but every time it happens the list is NOT scrolling.
Anybody have a fix or workaround?
I’m using the internal widget library, not the github version.
Jay
Same issue here, with build 2174…
“A row cannot be deleted whilst the tableView is scrolling”…
It’s not every time. It’s mainly when I first display the table, scroll it to the very end (I have a bottom padding), and try to delete the last row.
I tried a lot of thing:
-
Remove bouncing
-
Force scroll to stop using ScrollToY + performwithdelay for the delete
-
Test on real device
No success.
This is a bug. I don’t really have time to create a project to submit a bug. There is a lot of people complaining here, it’s definitely a bug and it should be took in account without need to be proved ;) .
I can understand your frustration. It’s not fun to create bug reports (and it takes valuable development time away), however for the guys at CoronaLabs to be able to fix a bug they need to be able to re-create it.
Having us file bug reports when we find a specific use-case that creates a problem is the best way to speed up the time it will take to fix the problem. Otherwise they’ll have to try to find a way to re-create a bug just from a description of it, which in most cases are futile and causes the bug to be pushed down in the priority queue.
If we can provide CoronaLabs with a test project that shows the bug in all its glory, then they can get right on the task of prioritizing and fixing it instead of having to “waste time” trying to figure out how to create a project of their own.
Try tableView._view._velocity = 0 before delete it should get you going until it is fixed.
Will try thank you!!
Same issue here, with build 2174…
“A row cannot be deleted whilst the tableView is scrolling”…
It’s not every time. It’s mainly when I first display the table, scroll it to the very end (I have a bottom padding), and try to delete the last row.
I tried a lot of thing:
-
Remove bouncing
-
Force scroll to stop using ScrollToY + performwithdelay for the delete
-
Test on real device
No success.
This is a bug. I don’t really have time to create a project to submit a bug. There is a lot of people complaining here, it’s definitely a bug and it should be took in account without need to be proved ;) .
I can understand your frustration. It’s not fun to create bug reports (and it takes valuable development time away), however for the guys at CoronaLabs to be able to fix a bug they need to be able to re-create it.
Having us file bug reports when we find a specific use-case that creates a problem is the best way to speed up the time it will take to fix the problem. Otherwise they’ll have to try to find a way to re-create a bug just from a description of it, which in most cases are futile and causes the bug to be pushed down in the priority queue.
If we can provide CoronaLabs with a test project that shows the bug in all its glory, then they can get right on the task of prioritizing and fixing it instead of having to “waste time” trying to figure out how to create a project of their own.
Try tableView._view._velocity = 0 before delete it should get you going until it is fixed.
Will try thank you!!
HI
when I have 5 rows and delete third row, fourth row doesn’t take the place of the third row but positions a bit closer to the second row. with evert deleting rows are getting closer and closer. what might it be?
thanks
Can you post a screen shot? Perhaps some code?
What version of Corona SDK are you running?
Rob
I’m using the latest version of SDK - I’ve just updated it today.
Here’s a video illustrating the problem:
https://www.dropbox.com/s/kzyqscxcz3e6wi7/corona_forum_video.mov
and a bit of code:
-- Handle row rendering local function onRowRender( event ) local phase = event.phase local row = event.row id = row.index -- print(data[event.row].done) -- Load or Create our settings box local thisRowText if row.index ==1 then thisRowText = data[1].name elseif row.index ==2 then thisRowText = data[2].name elseif row.index == 3 then thisRowText = data[3].name else thisRowText = "new stuff" end function onDeleteBtnTouch(event) list: deleteRow(row.index) print(row[2].rowHeight) end local rowTitle = display.newText( row, ".", 0, 0, row.contentWidth -200, row.contentHeight, native.systemFont, 25 ) rowTitle.text = thisRowText ---rowTitle:setReferencePoint(row.TopLeftReferencePoint) rowTitle.x =rowTitle.width\*0.5 + 100 rowTitle.y = row.contentHeight -50 rowTitle:setFillColor( 0, 0, 0 ) local deleteBtn = display.newImageRect( "circle.png", 40, 40 ) deleteBtn.x =rowTitle.x-350; deleteBtn.y = rowTitle.y; row:insert( deleteBtn ) deleteBtn:addEventListener( "touch", onDeleteBtnTouch ) -----boxes here end ---rowrender --Hande row touch events local function onRowTouch( event ) local phase = event.phase local row = event.target if "press" == phase then print( "Pressed row: " .. row.index ) elseif "release" == phase then print( "Tapped and/or Released row: " .. row.index ) end end --]] -- Create a tableView list = widget.newTableView { left = 0, top = 100, width = display.contentWidth , height = display.contentHeight , onRowRender = onRowRender, onRowTouch = onRowTouch, hideBackground = true, noLines = true, -- topPadding = display.contentHeight/10, bottomPadding = 0 } --Insert widgets/images into a group widgetGroup:insert( list ) -- insert rows into list (tableView widget) -- insert rows into list (tableView widget) for i = 1, 3 do local isCategory = false local rowHeight = 60 local rowColor = { default = { 255, 255, 255, 0 }, over = { 255, 255, 255, 0 } } -- Make some rows --]] list:insertRow { isCategory = isCategory, rowHeight = rowHeight, rowColor = rowColor, } end --- for iI am seeing the same problem. Starter v2014.2189 OS X v 10.9.2
Can you file a bug report please? Use the “Report a bug” link at the top of the page. Your test app will need to include your config.lua and your build.settings file and a minimal app that demonstrates the issue.
When you get the email back from the bug system, please post the bug numbers back here as a reference.
Thanks
Rob