Any enhanced list view patches?

Hello all,

Anybody remember any life-saving patches associated with enhanced list
views?  BTW, I have no reason to suspect any problems; I'm simply trying to
eliminate any possible causes of a machine lockup.  The relevant app does a
LOT of updating of an enhanced list view, hence my question.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

Bill,

> Anybody remember any life-saving patches associated with enhanced list
> views?  BTW, I have no reason to suspect any problems; I'm simply
trying to
> eliminate any possible causes of a machine lockup.  The relevant app
does a
> LOT of updating of an enhanced list view, hence my question.

This probably won't help, but FWIW:

I'd been having problems with ELVs -- Dolphin crashing under W98 -- when
Blair wrote:

> I'd pay particular
> attention to adding/deleting items in response to a notification from
a
> control. You might find that it is necessary to defer such an
operation
> (e.g. with queueDeferredAction:) until the notification has returned.

Since moving my update logic into deferred actions, I've had no further
problems.

See the thread started 1999/12/01, "GPF.  D3.03 & D3.04" (especially the
last few messages), for more detail.

> Bill

    -- chris

Chris,

> Since moving my update logic into deferred actions, I've had no further
> problems.
>
> See the thread started 1999/12/01, "GPF.  D3.03 & D3.04" (especially the
> last few messages), for more detail.

Thanks.  I'd found some earlier hints at similar problems and queued a few
things that might have been causing problems.  Generally I let the
background thread decide what changes it wants to make then then queue only
the update.  Thinking about it some more, it might be better to queue the
decisions as well; any thoughts either way?  For the app that has me
concerned about this, the background thread is the only interested party,
and it either: (1) updates one element of a list that's always the same; (2)
replaces the entire contents of the other list.  It's unlikely to hit a
problem with the list changing between decision and update.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

Bill,
> Generally I let the
> background thread decide what changes it wants to make then then queue
only
> the update.  Thinking about it some more, it might be better to queue the
> decisions as well; any thoughts either way?

I can't think of any reason why it should make a difference.  Sorry.

> Bill

    -- chris