Codejock Developer Community : Problem skinning CFileDialog

Problem skinning CFileDialog : Hi,now, I have found a dirty solution...

Thu, 16 May 2019 10:45:56 +0000

Author: cluster
Subject: 17016
Posted: 16 May 2019 at 10:45am

Hi,

now, I have found a dirty solution to disable the skin framework for the CFileDialog and CFolderPickerDialog. Better than nothing! ;-)

Problem skinning CFileDialog : Hi again,Skin Framework (Dark...

Tue, 14 May 2019 11:04:42 +0000

Author: cluster
Subject: 17016
Posted: 14 May 2019 at 11:04am

Hi again,

Skin Framework (Dark theme) and CFileDialog or CFolderPickerDialog are not compatible.

There is no good way to solve this issue.

I have figured out that, if you enable only the option xtpSkinApplyFrame and xtpSkinApplyMetrics and disable the AutoApplyNewWindow flag then you will get the "normal" look.

But i need to enable the xtpSkinApplyColors option as well.

So now, my idea was to disable this option before creating the file dialog and enable again, but then the whole app will flicker horrible.

XTPSkinManager()->SetApplyOptions(xtpSkinApplyFrame | xtpSkinApplyMetrics);
XTPSkinManager()->SetAutoApplyNewWindows(FALSE);

CFolderPickerDialog dlgFile();

dlgFile.DoModal()...

XTPSkinManager()->SetAutoApplyNewWindows(TRUE);
XTPSkinManager()->SetApplyOptions(xtpSkinApplyFrame | xtpSkinApplyMetrics | xtpSkinApplyColors);

Could you bring the FileDialog (IFileDialog) to a black list from the skin framework as you do with the "Internet Explorer" and "OleMainThread" for example?

Problem skinning CFileDialog : It is the same behavior as I have...

Sat, 04 Mar 2017 04:19:17 +0000

Author: cluster
Subject: 17016
Posted: 04 March 2017 at 4:19am

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:

Problem skinning CFileDialog : Can you please describe what exactly...

Fri, 03 Mar 2017 22:46:30 +0000

Author: astoyan
Subject: 17016
Posted: 03 March 2017 at 10:46pm

Can you please describe what exactly is not working for you with CFileDialog in details?

It is being used by many users and we we perform tests regularly, if it didn't work at all this would have been noticed and fixed already, so apparently it is specific to your use case. Have you tried to check any of our SkinFramework samples? If so, hasn't it still worked?

Regards,

Alexander

Problem skinning CFileDialog : I think I am the only one who...

Fri, 03 Mar 2017 11:10:42 +0000

Author: cluster
Subject: 17016
Posted: 03 March 2017 at 11:10am

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

Problem skinning CFileDialog : Hi Algae, thank you for your suggestion,...

Sat, 27 Aug 2016 09:22:52 +0000

Author: kstowell
Subject: 17016
Posted: 27 August 2016 at 9:22am

Hi Algae, thank you for your suggestion, I will if we can get this problem resolved with our next release.

Problem skinning CFileDialog : I gave up waiting for the promised...

Wed, 24 Aug 2016 15:52:49 +0000

Author: Algae
Subject: 17016
Posted: 24 August 2016 at 3:52pm

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.

Problem skinning CFileDialog : This issue has been fixed, the...

Sat, 18 Jun 2016 11:28:59 +0000

Author: agontarenko
Subject: 17016
Posted: 18 June 2016 at 11:28am

This issue has been fixed, the fix will be available in next beta or final release.

Regards,
Artem Gontarenko

Problem skinning CFileDialog : "On Windows 10, the sample...

Tue, 10 May 2016 03:46:41 +0000

Author: agontarenko
Subject: 17016
Posted: 10 May 2016 at 3:46am

"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.

Problem skinning CFileDialog : SvenC wrote:Plus: the edit...

Wed, 06 Apr 2016 03:48:26 +0000

Author: olebed
Subject: 17016
Posted: 06 April 2016 at 3:48am

SvenC wrote:

Plus: the edit controls (File name and directory combobox at top when putting the edit cursor inside) are too tiny. The height is not enough, so text gets clipped. There is a big white borders inside the controls while editing, so maybe it is just a wrong placement of the edit control inside the combo box.

This has been fixed, the fix will be available soon in v17.2
Topic: V17.1 Malformed skinnings