On Thu, Aug 07, 2003 at 12:53:00PM +0200, Andre Poenitz wrote:
> The proper fix are deep document iterators, a centralized cursor on top
> of that and stopping the abuse of LyXCursor for storing all kind of
> "interesting" information...
Absolutely. But now is most surely not the time to be expan
Andre, searching through a table that has not been traversed by the cursor
crashes. This is because by the time of the searchForward() call, the
cell's LyXText is *still* badly initialised. In particular, the
text->cursor.par() iterator points somewhere random because
text_.init(bv) has never fire
On Thu, Aug 07, 2003 at 01:23:16PM +0200, Andre Poenitz wrote:
> In January.
> In February.
> In March.
It's true, I'm a terrible bore ;)
john
--
Khendon's Law:
If the same point is made twice by the same person, the thread is over.
On Thu, Aug 07, 2003 at 12:18:13PM +0100, John Levon wrote:
> On Thu, Aug 07, 2003 at 12:53:00PM +0200, Andre Poenitz wrote:
>
> > The proper fix are deep document iterators, a centralized cursor on top
> > of that and stopping the abuse of LyXCursor for storing all kind of
> > "interesting" infor
On Wed, Aug 06, 2003 at 02:51:54AM +0100, John Levon wrote:
> Andre, searching through a table that has not been traversed by the cursor
> crashes.
I can't reproduce that, but this is certainly a bug.
> This is because by the time of the searchForward() call, the
> cell's LyXText is *still* badly
