Michael Gerz wrote:
Georg Baum wrote:
No, it does not fix a conversion, it suppresses a compiler warning. I
don't understand why x_ is of type double at all. Why not int?
I guess there are cases (like with multiple hfills), where x_ would be
incremented by a fraction of a pixel. If this happens several times and
we always strip the fraction, we get slightly incorrect output.
Looking at the code in lyxrow.[Ch] and rowpainter.C, I'd even say that
there is absolutely no reason for hfill and label_hfill to be double.
This can be optimized out by converting everything to int. But at the
same time, I don't think you'll get any speed improvment with this kind
of optimization. It might even be better to convert everything to double.
Abdel.
