Inset::localDispatch problem

2003-03-04 Thread Angus Leeming
Andr, as localDispatch is yours, perhaps you can help me with this problem. It's come up because I'm starting to deal with insets which have a dialog but which are also editable. Inset::localDispatch is called from LyXFunc::dispatch (below). If this fails then the LFUN is passed to

Re: Inset::localDispatch problem

2003-03-04 Thread Andre Poenitz
On Tue, Mar 04, 2003 at 11:16:39AM +, Angus Leeming wrote: André, as localDispatch is yours, Not really. perhaps you can help me with this problem. It's come up because I'm starting to deal with insets which have a dialog but which are also editable. Inset::localDispatch is called

Re: Inset::localDispatch problem

2003-03-04 Thread Angus Leeming
On Tuesday 04 March 2003 12:54 pm, Andre Poenitz wrote: The innermost level that knows to handle an event should handle it. Ideally there should not be (much|any) magical guessing who is responsible. The hierarchy should be something like LyXFunc BufferView Buffer OutermostText

Re: Inset::localDispatch problem

2003-03-04 Thread Juergen Vigna
Andre Poenitz wrote: The hierarchy should be something like LyXFunc | BufferView | Buffer | OutermostText [And this should go if everything is an inset] | Insets and we should walk it bottom-up. Currently we have some strange combination of guessing jumps down

Re: Inset::localDispatch problem

2003-03-04 Thread Andre Poenitz
On Tue, Mar 04, 2003 at 04:54:07PM +0100, Juergen Vigna wrote: I don't understand where you see jumps? bool BufferView::Pimpl::dispatch(FuncRequest const ev_in) { [...] default: return bv_-getLyXText()-dispatch(FuncRequest(ev, bv_)); } // end of switch } The

Inset::localDispatch problem

2003-03-04 Thread Angus Leeming
André, as localDispatch is yours, perhaps you can help me with this problem. It's come up because I'm starting to deal with insets which have a dialog but which are also editable. Inset::localDispatch is called from LyXFunc::dispatch (below). If this fails then the LFUN is passed to

Re: Inset::localDispatch problem

2003-03-04 Thread Andre Poenitz
On Tue, Mar 04, 2003 at 11:16:39AM +, Angus Leeming wrote: > André, as localDispatch is yours, Not really. > perhaps you can help me with this problem. It's come up because I'm > starting to deal with insets which have a dialog but which are also > editable. > > Inset::localDispatch is

Re: Inset::localDispatch problem

2003-03-04 Thread Angus Leeming
On Tuesday 04 March 2003 12:54 pm, Andre Poenitz wrote: > The innermost level that knows to handle an event should handle it. Ideally > there should not be (much|any) magical guessing who is responsible. > > The hierarchy should be something like > > LyXFunc > > BufferView > > Buffer > >

Re: Inset::localDispatch problem

2003-03-04 Thread Juergen Vigna
Andre Poenitz wrote: The hierarchy should be something like LyXFunc | BufferView | Buffer | OutermostText [And this should go if everything is an inset] | Insets and we should walk it bottom-up. Currently we have some strange combination of guessing jumps down

Re: Inset::localDispatch problem

2003-03-04 Thread Andre Poenitz
On Tue, Mar 04, 2003 at 04:54:07PM +0100, Juergen Vigna wrote: > I don't understand where you see jumps? bool BufferView::Pimpl::dispatch(FuncRequest const & ev_in) { [...] default: return bv_->getLyXText()->dispatch(FuncRequest(ev, bv_)); } // end of switch }