Thank you for the reply. It's nice to know the reason why this LaTeX file persists after I started using the newer versions of Asymptote. In particular, it's comforting to know that this is a known bug in recent Windows builds and not an error in my local Asymptote installation on my computer. The persisting LaTeX file is not giving me any major problems when using Asymptote; however, it's a bit inconvenient that it's no longer deleted automatically.
After updating from Asymptote 3.02 to 3.03, I can again use the -outname and -f png options in conjunction without getting an error. I am very grateful for this correction. Invoking Asymptote 3.03 with the -f png option still creates a LaTeX file with a filename consisting of the name of the asy file with an underscore appended. For instance, when I invoke the following from the command prompt: asy -noV -f png test a file "test_.tex" is created in the same folder. Please see the attached screenshot....
After updating from Asymptote 3.02 to 3.03, I can again use the -outname and -f png options in conjunction without getting an error. I am very grateful for this correction. Invoking Asymptote 3.03 with the -f png option still creates a LaTeX file with a filename consisting of the name of the asy file with an underscore appended. For instance, when I invoke the following from the command prompt: asy -noV -f png test a file "test_.tex" is created in the same folder. Please see the attached screenshot....
I have tested the use of -pngdriver=png16malpha when calling Asymptote from command line. It works well, and it produces the same transparent background as -pngdriver=pngalpha
Thank you very much for your quick reply. This solution works for me. Setting the PNG driver to "pngalpha" gives a transparent background in the PNG file, like I wanted.
I am using Asymptote 3.03 on Windows. When I export a 2D scene to PNG format, I get a white background instead of a transparent background. With older versions of Asymptote, exporting 2D scenes to PNG format yielded a transparent background, which is very convenient. As an example, consider an Asymptote file named "test.asy" which consists of the following single line of code: draw((0,0)--(100,100)); I then execute this file "test.asy" from Windows PowerShell using the following command: asy -noV...
I recently upgraded from Asymptote version 2.84 to version 3.02. When I export 2D graphics to PNG format, then Asymptote 3.02 creates a spurious .tex file in the same folder as the PNG file. The filename of the generated .tex file is the name of the exported PNG file with an underscore character appended. This happens when I run Asymptote on Windows 11. The generation of the .tex file causes an error when I invoke Asymptote from the command line with the "-outname" option. To reproduce this behavior,...
I recently upgraded from Asymptote version 2.84 to version 3.02. When I export 2D graphics to PNG format, then Asymptote 3.02 creates a spurious .tex file in the same folder as the PNG file. The filename of the generated .tex file is the name of the exported PNG file with an underscore character appended. This happens when I run Asymptote on Windows 11. The generation of the .tex file causes an error when I invoke Asymptote from the command line with the "-outname" option. To reproduce this behavior,...