User forums > Using Code::Blocks
Bad icons of C::B in the 16.01 release
ollydbg:
About the manifest file support, we can have two (the default embedded, and the standalone), and look at some document: Manifest embedded and external - which has priority? Can one override other? - Stack Overflow.
Under Windows XP, the standalone manifest file will take precedence, and other system(Win7 or Win10) will still use the internal one.
About the "click a menu assert", I haven't see it before 2015-12-xx, since to find the icon issue, I have switched from wx 3.0.2 to wx trunk after that day.
MortenMacFly:
--- Quote from: oBFusCATed on February 12, 2016, 08:47:00 pm ---Morten: Have you asked the wx devs if this change could be backported to WX_BRANCH_3_0?
--- End quote ---
IMHO it is already because its quite serious. I'll check - I've both is use.
MortenMacFly:
--- Quote from: ollydbg on February 13, 2016, 02:59:29 am ---Under Windows XP, the standalone manifest file will take precedence, and other system(Win7 or Win10) will still use the internal one.
--- End quote ---
If that is the case, it would be an easy fix, indeed. Can you verify its working and provide me with a manifest file so I can see how it affects windows 10, for example?
--- Quote from: ollydbg on February 13, 2016, 02:59:29 am ---About the "click a menu assert", I haven't see it before 2015-12-xx, since to find the icon issue, I have switched from wx 3.0.2 to wx trunk after that day.
--- End quote ---
Notice that this applied only to Windows >v8.1 I believe. The reason is that wx reports a wrong operating system version on those. Thus, some functions will work in "legacy" mode. There was a nice discussion about it on the wx patch tracker. But I don't have a link at hand...
MortenMacFly:
--- Quote from: MortenMacFly on February 13, 2016, 10:59:49 pm ---IMHO it is already because its quite serious. I'll check - I've both is use.
--- End quote ---
Yes, it is (see [wxWidgets]\src\msw\utils.cpp). so wxWidgets 3.0.3 (hopefully such thing will arrive soon) will have it fixed.
Edit: That is the fix, btw:
http://svn.wxwidgets.org/viewvc/wx/wxWidgets/branches/WX_3_0_BRANCH/src/msw/utils.cpp?r1=76715&r2=76714&pathrev=76715
ollydbg:
--- Quote from: MortenMacFly on February 13, 2016, 11:02:36 pm ---
--- Quote from: ollydbg on February 13, 2016, 02:59:29 am ---Under Windows XP, the standalone manifest file will take precedence, and other system(Win7 or Win10) will still use the internal one.
--- End quote ---
If that is the case, it would be an easy fix, indeed. Can you verify its working and provide me with a manifest file so I can see how it affects windows 10, for example?
--- End quote ---
Yes, it works here, I just add a file named codeblocks.exe.manifest, and it works fine with our 16.01 pre-build binary release.
You can use the one in my post: Re: Bad icons of C::B in the 16.01 release, also, you can just use the manifest file (x86.manifest) before the commit rev 10409.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version