On Mon, Nov 10, 2003 at 03:12:02PM +0100, Alfredo Braunstein wrote: > Andre Poenitz wrote: > > > I don't really know. I am still a bit confused about coordinates... > > Hum... it would be time to take a decision then? ;-) Are inset coordinates > relative to the parent or absolute?
I don't even have a gut feeling here... Another option would be to have absolute _screen_ coordinates for insets. > >> There is another problem I think: and it is the outer cursor getting > >> out-of-sync with where the real action is happening (if the action > >> happends inside an inset). > > > > Like asynchronous inset updates because the conversion finished? > > > > This should be harmless, they simply get ignored. But that's ok as they > > are off-screen anyway. Next time we come to that place, the paragraph > > (and scrollbar size) is adjusted. > > > > The only 'problem' is that the scrollbar position does not match exactly > > reality, but its 'not that bad'. > > > > > >> There are a few things that rely on that sync, and > >> shouldn't (fitCursor for instance). > > > > Anything else than the scrollbar issues? > > IIUC, it's worse than that, for instance fitCursor, and your recently > introduced getVisiblePars use the top old cursor (bv_->text->cursor), that > can be completely out-of-sync with where the action is happening, am I > right? Yes. But it's just for redrawing, nothing else. And we always redraw the whole screen. It's not bad if we miss an action because the cursor is too far off: It won't be visible anyway. Andre'
