3 replies to this topic

[RaduGrama]

I have an object that is being loaded in an async fashion and I cannot guarantee that it will be available by the time objectForSection is called. Is there a recommended approach for this type of situations?

[Tarek]

Hi Radu,

When object loading is asynchronous, you don't implement objectForSection, but rather directly set the section's 'boundObject' property as soon as the object is fetched. Please let me know if you still need help with this.

[RaduGrama]

Hi Tarek,

 

Thank you for you answer; I have a few questions/remarks on that:

• I'm assuming that's a safe approach, the documentation indicated that 'boundObject' should be used internally only, for subclassing?
• Can you describe the difference between 'boundObject', 'boundValue', and 'boundProperty'?
• And last, is it safe to call that multiple times? Or how would you handle a situation where you load asynchronously most of the object, then load another part of it as a separate asynchronous request (e.g. an image associated with the object)? Would you split that in two requests or would you just wait longer in a single request?

Thank you,

Radu

[Tarek]

Hi Radu,

 

Yes it's safe to call multiple times. Once set, the section will regenerate its cells, so you should be refreshing the associated table view to see your changes:

[myObjectSection.ownerTableViewModel.tableView reloadData];

 

As for the 'internal' label in the docs: as long as it says it's ok to use when subclassing, then it should be fine that you use it yourself