First off, thanks for the new widgets…the api and behavior tells me the code behind the scene’s is much cleaner and well designed. I can feel the solid engineering that went into to this.
Second, a few questions:
#1 I want my “onRowRender” function to be able to read-from (refer to) attributes on it’s parent (ie the TableView object itself). Making me use upvalues in onRowRender (ORR) prevents me from wrapping your objects with my own generic (and consistent) ORR function. It also prevents me from changing the row-rendering behavior later in places where the original upvalue data is out-of-scope. Can you tell me how (or create a hook) to access the parent TV obj from within ORR? Same request for onRowTouch…want to access the row’s containing TV parent.
#2 Can I change row-height on the fly (for example to display a nested sub-list under a row in the parent table view)? Other suggestions on how best to achieve an expanded “detail-pane” for a row below it while leaving the rest of the TableView in tact (and still scrollable)? I noticed in another thread that you might be working on dynamic row-creation and I realize that such a request as above makes your math substantially more complex.
#3 The docs do not clarify inner struct of the object type returned by the “new” widget methods. I see it’s a Table that has a _view table inside it? Is this analogous to the “.view” attribute we used to use to access the internal Display Object. If not, what’s the new way we access the top-most group containing the widget d-objs if we want to do something with them?
Third: Suggestions:
it’s clear that newPickerWheel uses newTableView internally. Can you give yourself a hidden method to call for this internal use case so I can override the public interface without breaking other widgets?