Note that NSTableView's delegate method -tableView:heightOfRow: allows you to create tables with rows of varying height. You might be able to just assign a column to the expander arrow button, which value you could use to track which rows are expanded.
Initially I was thinking on using this, but I think it would be complicated to completely customize it. Anyway I'll consider it as an option.
dws90 said:
Investigate NSCollectionView thoroughly before you commit to anything. The class has a lot of rough edges, and can be very, very confusing to get working.
Indeed I had a closer look in it and some points to consider are:
-Following Apple tutorial I could setup everything with bindings which is
great
-The Collection View has an adjustable limit of columns which is
great
-There is no default behavior on selecting, meaning one thing less to remove (from a Table View default behavior, for example),
great
-I could not find a way to change it's items heigh / opacity from hidden elements.
bad
I don't even know if that's possible!
dws90 said:
it's likely you could do it more easily from scratch.
That would be more fun, I would like to do that by the way. I've been searching for some examples to get started but none of them told me what I consider the "meat" of the class: stacking one view above the other. Any tips on that would be really appreciated.
Also, what worries me in this case is the memory management. If I start to show a large amount of cells (rows) with probably some graphics in it, wouldn't that represent a problem to memory?
Thank you by the help so far.