Widget 2.0 Tableview Change From Daily Build 1073 On

Solar2D Widgets
#21

Great!  I’ve been meaning to write a bug report about this issue, but haven’t gotten around to it.

As Danny is active on this thread, maybe this post will be enough?

If you put a print statement in the onRender function of the Corona TableView2 sample code you’ll see that isCategory=nil is being passed to the handler as the last event.

#22

I filed a bug a little while back (Case 22373), Danny should see this post and it should be enough.

Thanks again!

#23

Hi

I’ve the same problem

If I click on a row, I have a bug and the console print this message :

stack traceback:

    [C]: ?

    ?: in function ‘_manageRowLifeCycle’

    ?: in function <?:425>

    ?: in function <?:218>

Thanks

Olivier

#24

Any updates? I am not seeing that error but the UI is still broken(Category text never shows on top most category row)

#25

Hi

In CoronaSDK 2013.1092 (https://developer.coronalabs.com/release/2013/1092/)

it says : 

_Widget 2.0 - Fixed issue with tableView categories not passing isCategory to the rowRender function. Fixes casenum: 22373 _

_ 22373  _is the number of Chevol’s Bug

I installed Version 2013.1093 and I still have the bug I mentioned in my previous post

Chevol, do you still have your bug, or is it ok for you now?

Did I miss something?

Thanks for your help

Olivier

#26

I don’t know, I used ingemar’s solution and its been working for me so far. I’m afraid to go to 1093 because we should be launching soon and I don’t have time to deal with any new bugs at the moment. Print out the value of event.row.isCategory and if its nil when you get the error, then the issue still exists. Seeing if row.isCategory AND row.isCategory == nil before adding the category is what I used for a work around, look at my post above and let me know if that solves the isssue for now. 

Thanks again ingemar

#27

Thanks Chevol

#28

I’m using 1093, and I removed the “nil” check and it works.

#29

@oromanetti

I think that you’re seeing some other issue, as you get an error when you’re selecting a row.

#30

Thanks Ingemar, I think you’re right.

#31

@chevol

This happens only if the first row in the tableview is a category.

Sometimes you’ll see that event.row.isCategory is nil when passed to your handler (instead of true/false).

As a test you can scroll the tableview down with your finger. The category text will become visible, but as soon as the tableview retracts to its default position the category text will disappear.

You can get around the issue by handling the nil exception.

#32

@ingemar That’s the exact issue I am having! That also solved my issue, thanks!!!

Here is what I changed for anyone else having this issue:

if(event.row.isCategory==nil or row.isCategory)then --Render Category Row else --Render Row end
#33

Great!  I’ve been meaning to write a bug report about this issue, but haven’t gotten around to it.

As Danny is active on this thread, maybe this post will be enough?

If you put a print statement in the onRender function of the Corona TableView2 sample code you’ll see that isCategory=nil is being passed to the handler as the last event.

#34

I filed a bug a little while back (Case 22373), Danny should see this post and it should be enough.

Thanks again!

#35

Hi

I’ve the same problem

If I click on a row, I have a bug and the console print this message :

stack traceback:

    [C]: ?

    ?: in function ‘_manageRowLifeCycle’

    ?: in function <?:425>

    ?: in function <?:218>

Thanks

Olivier

#36

Hi

In CoronaSDK 2013.1092 (https://developer.coronalabs.com/release/2013/1092/)

it says : 

_Widget 2.0 - Fixed issue with tableView categories not passing isCategory to the rowRender function. Fixes casenum: 22373 _

_ 22373  _is the number of Chevol’s Bug

I installed Version 2013.1093 and I still have the bug I mentioned in my previous post

Chevol, do you still have your bug, or is it ok for you now?

Did I miss something?

Thanks for your help

Olivier

#37

I don’t know, I used ingemar’s solution and its been working for me so far. I’m afraid to go to 1093 because we should be launching soon and I don’t have time to deal with any new bugs at the moment. Print out the value of event.row.isCategory and if its nil when you get the error, then the issue still exists. Seeing if row.isCategory AND row.isCategory == nil before adding the category is what I used for a work around, look at my post above and let me know if that solves the isssue for now. 

Thanks again ingemar

#38

Thanks Chevol

#39

I’m using 1093, and I removed the “nil” check and it works.

#40

@oromanetti

I think that you’re seeing some other issue, as you get an error when you’re selecting a row.