Bug in PNG vignette generation about bluelatex HOT 7 CLOSED

Can you please describe the problem more precisely? What do you mean by 'vignette'? Is that a generated png page?

from bluelatex.

The file GetPngLet.scala contains the test: if (!pngFile.exists). It's a good test if the pdf hasn't change.
But if the PDF has change since the last vignette generation I'm not able to obtain the new version of the vignette.

'vignette' = generated png page

from bluelatex.

The png files should be cleaned when the paper was successfully compiled. See ebb326b

from bluelatex.

That solve the problem of new paper version but when the density change the image will not be regenerated.
It should perhaps add the density in the name of the image.

from bluelatex.

Actually I am not convinced it is something we want to change the density of the generated png. This feature does not make much sense to me and is more a legacy stuff than anything else.

@monperrus Do you really think this feature is still needed? What is the rationale behind it? Is it really used? With density of 100, it is sometimes barely readable, bigger is really huge and I am not sure this is used in practice.

from bluelatex.

I agree it isn't useful but the option is present in the API. Thus, it must work. The solution: remove this option.

(I can deal with a 100 density.)

from bluelatex.

Removing the density parameter fixed the problem to me, please reopen it if you think it did not

from bluelatex.