9732a89b6b
It controlled how the FilterConfigCache initialized, and also how the unused aFilterPath was initialized. The FilterConfigCache is reused, when there are other instances of GraphicFilter - so that means, that the "bUseConfig" flag doesn't necessarily mean that the initialization will happen as intended: the existing instance could have been initialized using the other value. Avoid this indeterministic behavior, and always use the config, except in fuzzing. The VCL tests, that could possibly once depend on that, now use config, so this is not an issue - and that means testing the same thing as used in the working code, not something different. Change-Id: I6555dc47328b362e020138cf454f5ede7f39d063 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/175894 Tested-by: Jenkins Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com> |
||
|---|---|---|
| .. | ||
| inc | ||
| langsupport | ||
| qa | ||
| source | ||
| uiconfig/ui | ||
| util | ||
| AllLangMoTarget_svt.mk | ||
| CppunitTest_svtools_dialogs_test.mk | ||
| CppunitTest_svtools_graphic.mk | ||
| CppunitTest_svtools_html.mk | ||
| Executable_langsupport.mk | ||
| IwyuFilter_svtools.yaml | ||
| JunitTest_svtools_unoapi.mk | ||
| Library_svt.mk | ||
| Makefile | ||
| Module_svtools.mk | ||
| README.md | ||
| UIConfig_svt.mk | ||
Tools on the Top of VCL
Common dialogs, file and print dialogs, wizards, vcl filters, lots of helper code.