I've checked several ways to bypass this problem (which, as I repeat, only occurs in the debug version): included the .rc in my .rc2 of the exe (where it appears in the resources within VS), the dlls (where the cursor does not appear in the dll resources), checked the release and the debug version, verified my settings, etc...

 

XTPResourceManager() looks for localization files, and I bet it finds one - which hasn't been updated with the new resource.

I'm currently working on a client's project who uses the Toolkit V13.01. In my installation, I use V13.21 (because I don't have the 13.01 installer anymore).

MFC and the toolkit are statically linked, no unicode but multibyte character set (so "SD" in this case).

Something weird is happening:

In the project I have an options dialog using the CXTPProptertyGrid class. Upon opening the dialog, CXTPPropertyGrid::CXTPPropertyGrid() is called which itself then calls "m_hCursorSplit = XTPResourceManager()->LoadCursor(XTP_IDC_VSPLITBAR);"

While the version compiled by the customer succeeds at this call, my own compile fails. The VSPLITBAR is not found with the error "[...]specific resource type cannot be found in the image file.".

To check if the resource (XTP_IDC_VSPLITBAR = 9971) is actually contained in the executable, I opened the .exe file in VS. This shows all resources within the executable. I clearly can see (and open within VS) that the bitmap is available under the Cursor resources.

The .rc2 file of my project contains the #include "XTToolkitPro.rc" entry.

I currently scratch my head because I cannot figure out, why the heck the cursor cannot be loaded.

If anyone has an idea, it would be greatly appreciated.

Edit: I just checked Release vs Debug version and it seems that either only the Debug version has the problem or the Release version simply ignores the load fail.

Thanks,

Stefan