Ah, that would explain it. Must have been some unintentional mistake by the plugin developer or some leftover from the previous (and actual) 2.0 version preceding the 1.2 one. Most of the times the focus is to make the plugin work as it should, and less on the final details that don't have that much to do with functionality... but yeah, these details can cause confustion indeed (and in this case, even functionality problems, if one mistakenly uses the "true" 2.0 version instead).A C++ plugin uses a .rc file to set the "properties" that Windows and Rainmeter gets. I'm guessing there is a 2.0 in the woodpile somewhere....Code:
#define APSTUDIO_READONLY_SYMBOLS#include <windows.h>#undef APSTUDIO_READONLY_SYMBOLS///////////////////////////////////////////////////////////////////////////////// Version//VS_VERSION_INFO VERSIONINFO FILEVERSION 3,0,0,0 PRODUCTVERSION 4,1,0,2989 FILEFLAGSMASK 0x17L#ifdef _DEBUG FILEFLAGS VS_FF_DEBUG#else FILEFLAGS 0x0L#endif FILEOSVOS_NT_WINDOWS32 FILETYPE VFT_DLL FILESUBTYPE VFT_UNKNOWNBEGIN BLOCK "StringFileInfo" BEGIN BLOCK "040904E4" BEGIN VALUE "FileVersion", "3.0.0.0" VALUE "LegalCopyright", "© 2018 - Jeffrey Morley" // Don't change the entries below! VALUE "ProductName", "Rainmeter"#ifdef _WIN64 VALUE "ProductVersion", "4.1.0.2989 (64-bit)"#else VALUE "ProductVersion", "4.1.0.2989 (32-bit)"#endif //_WIN64 END END BLOCK "VarFileInfo" BEGIN VALUE "Translation", 0x409, 1252 ENDEND
Statistics: Posted by Yincognito — Today, 3:10 pm
