>>>>> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Right now there is only one LyXView for one LyXFunc. There Abdelrazak> are two way forward for the multiple LyXView problem. Abdelrazak> 1) Application maintains a map of LyXFunc indexed by the Abdelrazak> LyXView ID as given but the Gui class when you create a Abdelrazak> new view. Abdelrazak> 2) We add a new member to FuncRequest (view_id_)that will Abdelrazak> be used only if this action is related to a LyXView. It Abdelrazak> would then be the used of the one unique Abdelrazak> LyXFunc::dispatch() method to dispatch the FuncRequest to Abdelrazak> the proper LyXView. Abdelrazak> I personnally think that 2) is more elegant because that Abdelrazak> will force us to clean up a bit more the dispatch Abdelrazak> machinery. But there might be other solutions out there so Abdelrazak> please, if you have an idea... I think I prefer 2) also. The only reason why we can need several lyxfuncs is for the state information needed by keysym processing. JMarc
