Le 10/04/2017 à 01:00, Uwe Stöhr a écrit :
El 06.04.2017 a las 11:10, Jean-Marc Lasgouttes escribió:
That is not how it works. Actually, I propose to add a rule to our
coding rules that says that no code which does not take in account
zoom and DPI when drawing should be accepted (with the usual
exceptions, of course).
I have not heard about this rule.
This is why there is the word "propose" in the sentence above.
I also sent the patch to the list for
some days before I put it in. I haven't got this info from you.
This is why I did not complain about that. But it is not because a patch
is in that it is immune of of code review (especially when there are
user-visible issues).
I don't get it. Seems that I have been away for too long. At first, yes
I can read TeX code, yes I experimented with painting including the
zoom.
I could not find a better solution that I proposed. When zooming out a
lot one got no stroke at all.
I implemented this for you now at 94114fd1. It is even a little bit
shorter than the original code, I do not think that the price to pay was
so high for something correct.
However, I still think that we should not leave the WYSIWYM track in
favor of WYSIWYG. The number of strokes is not important within LyX. The
user should see that there will be strokes and that is it. That is the
WYSIWYM concept.
WYSIWYM is not about "I have the right to give an ugly screen output",
it is about having a visually pleasant output that tells you what your
output in a meaningful way. The only difference with WYSIWYG is that
some things (labels, footnotes, line breaks) are not represented
visually, but semantically.
As I understand you, you want me to use the currently
selected screen font to draw a '/' character over the text that is
repeated by 0.35em (in pixels). That is quite complicated (at least for
me) and I don't see the benefit. That would be WYSIWYG. Is this really
necessary?
You got it wrong. What I say is a _requirement_ is to have a good output
at a high zoom level (this is a good way to see what HiDPI users will
see). Now, how do I find a nice way to have good output at high DPI?
Wait, LaTeX does output at high DPI !! Let's see what it does and do the
same if it is not too complicated!
So, what I mean is that mimicking LaTeX is not a requirement, it is a
trick to help you. And don't come tell me that the new code is more
complicated than the old one, because it is not.
Now, what I would like to see is some action on the lefteqn patch ;)
JMarc
