On Mon, Aug 11, 2003 at 09:54:06AM +0100, John Levon wrote:
> On Mon, Aug 11, 2003 at 10:40:08AM +0200, Andre Poenitz wrote:
>
> > lyxerr << "BufferView::update()" << endl;
> > + // fix cursor coordinate cache in case something went wrong
> > + if (bv_->getLyXText()) {
> > + // c
On Mon, Aug 11, 2003 at 11:07:25AM +0200, Andre Poenitz wrote:
> Instead of having this kind of hack in 20 places, one place is better.
True... but it could perhaps be flagged up ?
> Care to explain what's wrong with that?
This is clearly labelling a massive problem with the current cursor
code
On Mon, Aug 11, 2003 at 10:40:08AM +0200, Andre Poenitz wrote:
> lyxerr << "BufferView::update()" << endl;
> + // fix cursor coordinate cache in case something went wrong
> + if (bv_->getLyXText()) {
> + // check needed to survive LyX startup
> + bv_->getLyXTe
On Mon, Aug 11, 2003 at 10:10:59AM +0100, John Levon wrote:
> On Mon, Aug 11, 2003 at 11:07:25AM +0200, Andre Poenitz wrote:
>
> > Instead of having this kind of hack in 20 places, one place is better.
>
> True... but it could perhaps be flagged up ?
Ok.
Actually I think it is needed in one pla
On Mon, Aug 11, 2003 at 11:21:24AM +0200, Andre Poenitz wrote:
> > This is clearly labelling a massive problem with the current cursor
> > code: that is, you cannot just set the cursor at abritrary x,y and
> > expect the inset locking to place the cursor there.
>
> There is no such problem in ma
