In 0.115 and previous, using the project_name field in settings would be reflected in the name of the resulting .html file. I just updated to 0.120 and it appears that project_name is only lending itself to the name of the resulting image files, but not the html file.
For instance, with 0.120 a file named foo.ai with a project_name: bar yields the following two files (if there's only one artboard):
bar.htmlfoo-Artboard_1.png
In previous iterations, the resulting files would both reflect the project name setting, such as:
foo.htmlfoo-Artboard_1.png
This may be intentional but if not, I wanted to flag.
In 0.115 and previous, using the
project_namefield in settings would be reflected in the name of the resulting .html file. I just updated to 0.120 and it appears thatproject_nameis only lending itself to the name of the resulting image files, but not the html file.For instance, with 0.120 a file named
foo.aiwith aproject_name: baryields the following two files (if there's only one artboard):bar.htmlfoo-Artboard_1.pngIn previous iterations, the resulting files would both reflect the project name setting, such as:
foo.htmlfoo-Artboard_1.pngThis may be intentional but if not, I wanted to flag.