I really use it because I'm developing an NSIS UI header, and certain functions have macros that need to be restricted in their usage, for example one of the macros is to only allow them to be used within a specific callback function, and that's where using ${__FUNCTION__} would be perfect. Currently !searchreplace has been used to remove the “.” from the result. , temporarily defining a symbol and comparing it. Of course, I could also write an extra judgment statement not to modify the result. As...
I really use it because I'm developing an NSIS UI header, and certain functions have macros that need to be restricted in their usage, for example one of the macros is to only allow them to be used within a specific callback function, and that's where using ${__FUNCTION__} would be perfect. Currently !searchreplace has been used to remove the “.” from the result. , temporarily defining a symbol and comparing it. Of course, I could also write an extra judgment statement not to modify the result. As...
Bug: LicenseBkColor doesn't work in uninstallers
Bug: Inconsistency in the value of ${__FUNCTION__}.
Upon careful comparison, the problem was found: There is an extra space after this line, and the problem is solved by deleting it. SimpChinese.nlf line: 142 TradChinese.nlf line:144 By the way, all language files were checked one by one, and the language files with extra spaces at the end of the lines were found as follows: SimpChinese.nlf TradChinese.nlf Belarusian.nlf Georgian.nlf Tatar.nlf Uzbek.nlf
Upon careful comparison, the problem was found: There is an extra space after this line, and the problem is solved by deleting it. SimpChinese.nlf line: 142 TradChinese.nlf line:144 By the way, all language files were checked one by one, and the language files with extra spaces at the end of the lines were found as follows: SimpChinese.nlf TradChinese.nlf Belarusian.nlf Georgian.nlf Tatar.nlf Uzbek
TradChinese Randomly tested several other languages, all without the extra ""
SimpChinese