>"Vincent van Ravesteijn - TNW" <v.f.vanraveste...@tudelft.nl> writes: >> 1. If we want to use the AtPoint mechanism for this, we should take >> this argument into account when deciding to which Inset to relay. This >> would mean to put lfun-specific code into LyXAction::dispatch (IIRC),
>> which is ugly. > >The note inset can look at the argument and, if it is not equal to >"note", tell via getStatus that it does not want to handle this lfun. >Why is this complicated? Hmm.. Maybe you just solved my problem. Looking at the AtPoint code I realize that I might have forgotten to call cur.undispatched(). Without this call, the lfun is never relayed to the current inset after it has been dispatched to the next inset. If this is the problem indeed, I'm sorry for making you worry. You made the AtPoint thingie more intelligent than I realized. >Jmarc Vincent P.S I'm also annoyed by the difference between dispatch() and getStatus(). Namely one of them returns a bool to indicate whether a definitive decision has been made, whereas the other uses the cur.dispatched_ member.
