Andre Poenitz wrote:
> It still looks as if update() has a tendency to get expensive if certain > nice-to-have or necessary features are triggered from there. Also note that we don't need to fire an update on every cursor movement, which is the biggest problem. I've just seen your #warning, but I've no clue of what's the problem. Ah, maybe entering/exiting insets should fire an update nevertheless? So should we add some checks directly in the lfun handlers? Alfredo
