Problem skinning CFileDialog

I see the exact same issue. Also if you click the arrow next to the button that changes the view, you get this funny looking popup that is half skinned.

I can still confirm the wrong left lower corner for 15.0.2 too.
Any progress or suggestions about this?

Is this http://forum.codejock.com/forum_posts.asp?TID=18052&KW=skinbuilder&PID=63310&title=codejock-style-template#63310 related (and therefore fixed) to this problem?

Hello,

Oleg, I don't mean the black line, it's about the gripper fragment at the right bottom corner when dlg is NOT skinned.
I know that you can't do anything on the black lines which are caused by MS special - that has been already discussed in some other forums in the net.

@Willowmaster: skinning is done via .cjstyle file, but in this case the dlg skinning is disabled but the blue gripper is still there.

Hello everybody,

Is this fixed in 16.2.4?

I hesitate to port all my library fixes/changes unless this is the case.

Thanks!

I have the same problem with the CFileDialog and skin framework.
I use a dark theme skin and if I switch off by
XTPSkinManager()->SetAutoApplyNewWindows(FALSE);
CFileDialog fileDlg(TRUE);
fileDlg.DoModal();
XTPSkinManager()->SetAutoApplyNewWindows(TRUE);
I will get this behavior:

Same in 17.1.0.

I really gave up skinning this file dialog. It has never been working well.
Unfortunately with skinning disabled, as described in my initial post above, the bottom right blue corner still remains. Tested with 17.1.0

CJ, can you please try to fix this issue either way? Thanx!!

"On Windows 10, the sample "SkinCommCtrl" has a wrong context menu in standard FileOpen dialog" - This has been fixed, the fix will be available in next beta or final release.

I gave up waiting for the promised fix for "Windows 10 context menu in standard FileOpen dialog" where the right click menu is chopped into a narrow band.

After some experimentation, I devised a solution.

A little background first. I have been unable to use anything later than CJ 16.26 due to a number of critical flaws. That being said, you may or may not require the GetVersion replacement function described below.

The following should make the Windows 10 context menu both skin and function normally:

1. First we replace the Windows 10 disastrous GetVersion code so we actually know what OS it is.

Add this at the end of your Application header file. This should give you a working function to see if the client machine is Win 10.

AFX_INLINE BOOL EqualsMajorVersion(DWORD majorVersion)
{
    OSVERSIONINFOEX osVersionInfo;
    ::ZeroMemory(&osVersionInfo, sizeof(OSVERSIONINFOEX));
    osVersionInfo.dwOSVersionInfoSize = sizeof(OSVERSIONINFOEX);
    osVersionInfo.dwMajorVersion = majorVersion;
    ULONGLONG maskCondition = ::VerSetConditionMask(0, VER_MAJORVERSION, VER_GREATER_EQUAL);
    return ::VerifyVersionInfo(&osVersionInfo, VER_MAJORVERSION, maskCondition);
}

2. Next, add the following to your program initialization as shown:

BOOL CMyApp::InitInstance()
{
// initialize various things
...

// I inserted right after this line
LoadStdProfileSettings();  // Load standard INI file options (including MRU)

if ( EqualsMajorVersion(10) )
        XTPSkinManager()->SetApplyOptions(xtpSkinApplyMetrics | xtpSkinApplyColors | xtpSkinApplyFrame);

...
// continue initializing
}

The SkinManager Apply Options must be set to make the dialog work properly.

As always, your mileage may vary but it worked for me.

I think I am the only one who wants to use the CFileDialg together with skin framework.
It doesn't work with enable skin framework nor with disable by XTPSkinManager()->SetAutoApplyNewWindows(FALSE);
I mean is there an alternative for the CFileDialog???

Windows 7
Visual Studio 2010
CodeJock 17.3

It is the same behavior as I have descripted already in my last post here for almost one year...
And if I enable the skin framework with dark theme it looks like this: