I've played a bit with coordinates this morning, and tried to bring LyX
again to a working state (coord-wise). I think it can be a good starting
point to choose a right coordinate scheme.
currently is:
- LyXFunc::dispatch uses screen coords (ok)
- BufferView::Pimpl::workAreaDispatch receives sc
On Thu, Feb 05, 2004 at 12:43:23PM +0100, Alfredo Braunstein wrote:
> I've played a bit with coordinates this morning, and tried to bring LyX
> again to a working state (coord-wise). I think it can be a good starting
> point to choose a right coordinate scheme.
>
> currently is:
>
> - LyXFunc::d
Andre Poenitz wrote:
> On Thu, Feb 05, 2004 at 12:43:23PM +0100, Alfredo Braunstein wrote:
>> I've played a bit with coordinates this morning, and tried to bring LyX
>> again to a working state (coord-wise). I think it can be a good starting
>> point to choose a right coordinate scheme.
>>
>> cur
On Thu, Feb 05, 2004 at 01:13:12PM +0100, Alfredo Braunstein wrote:
> > I'd think we should settle here for a clear scheme, i.e. either absolute
> > or screen-relative.
>
> screen-relative is out of the question: it's clearly worse than absolute.
> The only things that can use screen-relative coor
Andre Poenitz wrote:
>> For internal things LyXText-relative, or par-relative is fine I think (as
>> long as things remain somewhat private).
>
> Which 'internal things' do you mean?
row/par y-pos. It's faster to keep things relative to par/lyxtext (I think
it has shown on the profiles, right?)
On Thu, Feb 05, 2004 at 01:23:11PM +0100, Alfredo Braunstein wrote:
> Andre Poenitz wrote:
>
> >> For internal things LyXText-relative, or par-relative is fine I think (as
> >> long as things remain somewhat private).
> >
> > Which 'internal things' do you mean?
>
> row/par y-pos. It's faster to
