Jean-Marc Lasgouttes wrote: > The problem with insetinfo is that havbing to update this information at > every keystroke can be expensive, unless of course the value is not shown > in the edit window (but then you know that this is the next thing people > would ask for...).
Bummer indeed. > OTOH, it would make sense to have an InsetInfo instance that shows the > result of an lfun (probably maked as Embedable in LyXAction.cpp to avoid > problems). Plus time when it needs to be updated. Pavel
