>>> 3) let the LFUN dispatch in lyxfind.cpp return the required >>> information (match position and length) to the caller; for example, >>> by means of a DispatchResult sub-class (any strong objection to >>> adding a "DispatchResult &" to some of the existing ::dispatch() >>> methods? >>> >> I think this is something we have been meaning to do anyway. At the >> moment, the DispatchResult argument is where it has been needed, or >> where JMarc (usually) suggested I should put it. > >Putting it in FuncRequest would make sense to me. > >But it seems that the rest of the discussion implies that we do >not need to do it yet?
So, why are we discussing it then .. Because we need it ? Isn't the use of cur.dispatched(), cur.undispatched(), cur.result().dispatched() basically a work-around for missing the DispatchResult which only works in places where there is a Cursor available ? If so, then it has been needed already in a lot of places. >Jmarc Vincent
