Codejock Forums Homepage
Forum Home Forum Home > Codejock Products > Visual C++ MFC > Toolkit Pro
  New Posts New Posts RSS Feed - 17.3 themes are complete broken Win10
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

17.3 themes are complete broken Win10

 Post Reply Post Reply
Author
Message
hakoar View Drop Down
Groupie
Groupie
Avatar

Joined: 06 August 2008
Location: Finland
Status: Offline
Points: 21
Post Options Post Options   Thanks (0) Thanks(0)   Quote hakoar Quote  Post ReplyReply Direct Link To This Post Topic: 17.3 themes are complete broken Win10
    Posted: 25 October 2016 at 11:41am
My application was already broken with 17.2 on Windows 10 but this 17.3 is even more so?
Even sample programs cannot use themes as they should?
What kind of testing was done before this was released?
I'm loosing my patience....

 
Back to Top
hakoar View Drop Down
Groupie
Groupie
Avatar

Joined: 06 August 2008
Location: Finland
Status: Offline
Points: 21
Post Options Post Options   Thanks (0) Thanks(0)   Quote hakoar Quote  Post ReplyReply Direct Link To This Post Posted: 25 October 2016 at 11:47am
Note!
It's 64-bit unicode static compilation of the sample...

Back to Top
olebed View Drop Down
Admin Group
Admin Group


Joined: 01 July 2014
Location: Ukraine
Status: Offline
Points: 841
Post Options Post Options   Thanks (0) Thanks(0)   Quote olebed Quote  Post ReplyReply Direct Link To This Post Posted: 28 October 2016 at 1:09pm
Hello,

Please explain how do you configure the environment and projects  to get this result.

In your screenshot I can see that elements which are not drawn  are drawn with our inner font  as symbols (primitives). So I can suppose that font is not loaded.  I can reproduce this and get assertion in loading font in CXTPPrimitiveDrawer::InitFont()   when I 

1) add to  Controls project ToolkitProStatic.dsp;
2) create new configuration  for Controls project "Static Unicode Debug" which inherits from "Unicode Debug";
3) add in paths  "Static_"
4) add _XTP_STATICLINK  to Properties of project -> Configuration Properties > C/C++ > Preprocessor > Preprocessor Definitions
5) in Configuration Manager for ToolkitProStatic project set "Dynamic Unicode Debug" configuration ("Static Unicode Debug" should be used with other settings as you will see below)

6) build this, run, and get ASSERTION in CXTPPrimitiveDrawer::InitFont(). For DEBUG configuration it will be assertion but for RELEASE there will be empty places on some controls.

7) So I suggest that you don't set
  'Configuration Properties'->General->'Use of MFC'->'Use MFC in a Static Library'

  and for debug configurations: 
  'Configuration Properties' -> 'C/C++' -> 'Code generation' -> 'Runtime Library' -> 'Multi-threaded Debug (/MTd)'

  or for release configurations:
  'Configuration Properties' -> 'C/C++' -> 'Code generation' -> 'Runtime Library' -> Multi-threaded (/MT)

8) also _XTP_STATICLINK no needed anymore in Preprocessor Definitions
9) in Configuration Manager for ToolkitProStatic project set "Static Unicode Debug" configuration.

Regards,
 Oleksandr Lebed
Back to Top
olebed View Drop Down
Admin Group
Admin Group


Joined: 01 July 2014
Location: Ukraine
Status: Offline
Points: 841
Post Options Post Options   Thanks (0) Thanks(0)   Quote olebed Quote  Post ReplyReply Direct Link To This Post Posted: 28 October 2016 at 3:26pm
Note: If using the Xtreme Toolkit Pro as a static library linked to an application that is dynamically linked with MFC, you will need to do next changes in Controls sample project:

1) build ToolkitProStatic project in "Dynamic Unicode Release" configuration
2) Add the following lines of code to your stdafx.h file:
 #define _XTP_STATICLINK
 #include "XTToolkitPro.h"

3) Add the following line of code to your *.rc2 file after the comment:
  // "Add manually edited resources here...":
  #include "XTToolkitPro.rc"

4) create new configuration  for Controls project "Dynamic Unicode Release" (copy from "Unicode Release");
5) add "Dynamic_" in all output paths in properties of project (in 'Configuration Properties' > 'C/C++' > ..   and 'Configuration Properties' > General > 'Intermediate Directory')
6) after copying configuration from "Unicode Release" next properties will be correct
'Configuration Properties' > General > 'Use of MFC' > 'Use MFC in a Shared DLL'
'Configuration Properties' > 'C/C++' > 'Code generation' > 'Runtime Library' > 'Multi-threaded DLL (/MD)'
7) build Controls sample.


Also I write clearly changes for Static linking  MFC and ToolkitPro
1) build ToolkitProStatic project in "Static Unicode Release" configuration
2) Exclude the following line of code from your stdafx.h file or from Preprocessor Definitions:
 #define _XTP_STATICLINK
 
3) Exclude the following line of code to your *.rc2 file after the comment:
  #include "XTToolkitPro.rc"

4) create new configuration  for Controls project "Static Unicode Release" (copy from "Unicode Release");
5) add "Static_" in all output paths in properties of project
6) 'Configuration Properties' > General > 'Use of MFC' > 'Use MFC in a Static Library'
7) 'Configuration Properties' > 'C/C++' > 'Code generation' > 'Runtime Library' > 'Multi-threaded (/MT)'
7) build Controls sample.
Back to Top
hakoar View Drop Down
Groupie
Groupie
Avatar

Joined: 06 August 2008
Location: Finland
Status: Offline
Points: 21
Post Options Post Options   Thanks (0) Thanks(0)   Quote hakoar Quote  Post ReplyReply Direct Link To This Post Posted: 31 October 2016 at 4:07am
Hi,
The environment is what it is after running the Toolkit "deployment tool".
No changes made to the environment after installation.
So, the Toolkit deployment tool is then broken?

Back to Top
hakoar View Drop Down
Groupie
Groupie
Avatar

Joined: 06 August 2008
Location: Finland
Status: Offline
Points: 21
Post Options Post Options   Thanks (0) Thanks(0)   Quote hakoar Quote  Post ReplyReply Direct Link To This Post Posted: 31 October 2016 at 4:11am
I'm trying to compile 64-bit statically linked unicode application, I just need the instructions of how to make my existing app to be compiled correctly with the latest toolkit?
It's been fine as it is since v16.x. but after v17 it's been broken :-(.


Back to Top
hakoar View Drop Down
Groupie
Groupie
Avatar

Joined: 06 August 2008
Location: Finland
Status: Offline
Points: 21
Post Options Post Options   Thanks (0) Thanks(0)   Quote hakoar Quote  Post ReplyReply Direct Link To This Post Posted: 31 October 2016 at 4:13am
Oh, btw. the Toolkit's own deployment tool has this same problem! It doesn't show the checkbox marks at all when the "select compilers" list is shown...

Back to Top
hakoar View Drop Down
Groupie
Groupie
Avatar

Joined: 06 August 2008
Location: Finland
Status: Offline
Points: 21
Post Options Post Options   Thanks (0) Thanks(0)   Quote hakoar Quote  Post ReplyReply Direct Link To This Post Posted: 31 October 2016 at 4:35am
Here's a screenshot of the Deployment tool which shows this same BUG!
See, all is selected but NO checkbox is shown?



Back to Top
olebed View Drop Down
Admin Group
Admin Group


Joined: 01 July 2014
Location: Ukraine
Status: Offline
Points: 841
Post Options Post Options   Thanks (0) Thanks(0)   Quote olebed Quote  Post ReplyReply Direct Link To This Post Posted: 31 October 2016 at 4:44am
What version of your Visual Studio ? 2015 as in screenshot ?

What other options have you chosen on deployment ?
Back to Top
hakoar View Drop Down
Groupie
Groupie
Avatar

Joined: 06 August 2008
Location: Finland
Status: Offline
Points: 21
Post Options Post Options   Thanks (0) Thanks(0)   Quote hakoar Quote  Post ReplyReply Direct Link To This Post Posted: 31 October 2016 at 5:26am
Here are the options selected:



Back to Top
olebed View Drop Down
Admin Group
Admin Group


Joined: 01 July 2014
Location: Ukraine
Status: Offline
Points: 841
Post Options Post Options   Thanks (0) Thanks(0)   Quote olebed Quote  Post ReplyReply Direct Link To This Post Posted: 01 November 2016 at 7:50am
We can't reproduce your results from first screenshot without changes in configuration.

Also Deploy application doesn't use codejock's controls, so it is may be problem in your environment. Try to update Windows and Visual Studio.
Back to Top
hakoar View Drop Down
Groupie
Groupie
Avatar

Joined: 06 August 2008
Location: Finland
Status: Offline
Points: 21
Post Options Post Options   Thanks (0) Thanks(0)   Quote hakoar Quote  Post ReplyReply Direct Link To This Post Posted: 01 November 2016 at 11:06am
All my laptop sw is up-to-date. Nothing broken there.

Back to Top
SvenC View Drop Down
Groupie
Groupie


Joined: 02 February 2007
Status: Offline
Points: 79
Post Options Post Options   Thanks (1) Thanks(1)   Quote SvenC Quote  Post ReplyReply Direct Link To This Post Posted: 01 November 2016 at 12:03pm
The deployment wizard checkbox sometimes needs a double click on my system (Win 10 x64 14393 with current updates). Bit unusual behavior of a checkbox.

While mouse clicks toggle the check mark visibility correctly, the "None" button leaves a bit of the check mark on the screen.

Guess it is due to DPI scaling: I use a DPI scaling of 125%.

And I use the Windows 10 DPI fix tool, to get the scaling algorithm of Win 8.1 (http://windows10_dpi_blurry_fix.xpexplorer.com/) to avoid blurry text in older Windows apps (mmc.exe, cmd.exe...).


--
SvenC

Toolkit Pro 15.3.1, 16.2.4, 16.3.1, 16.4.0, 17.2.0, 17.3.0, 18.0.1, 18.2 with VC++ 2010, 2012, 2013, 2015, 2017
Back to Top
agontarenko View Drop Down
Admin Group
Admin Group


Joined: 25 March 2016
Status: Offline
Points: 260
Post Options Post Options   Thanks (0) Thanks(0)   Quote agontarenko Quote  Post ReplyReply Direct Link To This Post Posted: 02 December 2016 at 10:16am
Hello,

I'm glad to inform you that the issue with broken checkbox in Deploy Wizard was fixed.
Additionally I want to say, what problem with deploy wizard not depend on Codejock library.

Regards,
Artem Gontarenko
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.141 seconds.