This is an very interesting idea. The only problem I can see is for
undoing. I could begin a transaction before showing the view and
commit or rollback accordingly. I need to explore the potentials
problems of keeping a transaction open for a theoretically long time
though. This to cover th
On Fri, Oct 31, 2008 at 6:37 PM, Andre Masse <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a datasource for an NSTableView which is a NSMutableArray (call it
> mainArray for the moment) and I'm not sure which way is better to manage
> add, update and delete rows. I can use either one array for each o
Sorry for the confusion. English is not my natural language and it's
been a long week :-) Also the subject should really be about
synchronizing data in the table view with a database back-end. This
the "tracking changes" I need to work on.
I'll try to make this clearer. As an analogy, let's
On 1 Nov 2008, at 9:37 am, Andre Masse wrote:
I have a datasource for an NSTableView which is a NSMutableArray
(call it mainArray for the moment) and I'm not sure which way is
better to manage add, update and delete rows. I can use either one
array for each of those cases or add a field to
Hi,
I have a datasource for an NSTableView which is a NSMutableArray (call
it mainArray for the moment) and I'm not sure which way is better to
manage add, update and delete rows. I can use either one array for
each of those cases or add a field to the mainArray (like 1 for new, 2
for upd
