Andre Poenitz wrote: >> why mouse clicks? > > Mostly because that's the area where the current architecture differs > most from the IL architecture. With IL we had 'four phase' dispatch in > the 'complicated' insets: First a switch to try to make sense of mouse > events, then calling the_locking_inset->dispatch, then special handling > by the inset and finally pass to the LyXText's dispatch. > > Nowadays we just have one big switch with special inset handling and the > default branch dispatches to the LyXText. The first two phases are > basically moved to the global cursor. This is much simpler, but the > replacement for the first phase is not yet functional.
Thanks for the explanation. For handling mouse clicks globally we'll need/have some machinery to iterate over all insets in the doc (including embedded ones), right? Or otherwise I guess that 'heavy' insets will still have to take care of their own dispatching 'down' to their embedded childs? > We are 80% through, apart from the mouse it's just straightforward stuff > left. I'll take care of the mouse stuff myself. The rest may take a > few days due to the amount of code involved, but generally there are no > ugly corner cases involved, so it should get straightened out quickly. I'm tempted to believe you ;-) > I've already math now back in a working state btw. Cool. Alfredo
