On Wed, Nov 22, 2006 at 05:58:20PM +0100, Georg Baum wrote: > <nicefrac> > <cell logicalrow="0" logicalcol="0">1</cell> > <cell logicalrow="1" logicalcol="0">2</cell> > </nicefrac>
That's basically waht idxUp/Down does. > >> like that. IIRC the brutefind methods were introduced as a fallback hack > >> and never intended to be really used, because the normal find methods > >> should always work. > > > > So, anyone remember is there was any plan to replace that. > > IIRC there was no plan. Andre simply stated that this solution is not good. Because I tried and there was real negative feedback. In fact, I pretty much started out the same direction as Abdel does today. Ripping out stuff and watch what fails as a means to discover the inner working of things is surely not his invention.... > > The problem here is that sometimes we need something that is not on > > screen but that we should have calculated anyway. This happens for > > example when you have a formula that is only half displayed at the > > bottom of the screen. I am not sure how this is handled by the > > CoordCache but it seems that only what is on screen is in the CoordCache > > (I might be wrong here). > > I don't know either, but in that case it should be possible to first scroll > a bit and then go down and find the inset. If I press 'down' at the bottom > of the screen it is obvious that scrolling is needed, so it could be done > first and then it could be found out where exactly the cursor goes. I think it should never, evre happen, even today. > >> I don't know the > >> implementation too well, > > > > I guess nobody really knows... except Andre' :-( > > And Alfredo. Indeed. After all, he used to fix the mess I left behind... Andre'
