Join GitHub today
Infusion X - Alternate Styles/ Theme: John Wick/ Theme: LoL GAME VS/ Theme: Obsidian Gal/ Theme: Overwatch/ Theme: Radeon - Join the Rebellion/ Theme.gitattributes: CC-BY-NC-ND 4.0.rtf: Creative Commons.png: LICENSE: README.md. Win 10 3rd Party Visual Style Themes w/ UXStyles or Ultra UX Patcher I read somewhere that Visual Styles themes made for Win 8.1 will work on Win 10 using either the patch UXstyles (which works by retaining settings in memory) or 'Ultra UX Theme Patcher' (which physically changes/replaces certain system files but allows you to restore original files.).
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Apr 9, 2018
Following one of the following strategies: |
![Visual Visual](/uploads/1/2/4/9/124996600/772033483.png)
commented Apr 9, 2018 • edited
edited
it makes things look better |
commented Apr 10, 2018
This is the first thing that came to my mind. Windows 10's visual style is much closer to the classic visual style but is less cluttered due to the unnecessarily onlines being removed. Adding visual style support will keep the authentic feel in Windows 10 while keeping the app looking cleaner and easier on the eyes. The eye is distracted from unnecessary things, and a cleaner and focused UI allows the brain to focus better. We as have learned a great deal about good UI design over the last decades, and we now undesirable the true value of a clean UI. |
commented Apr 10, 2018
What are the nature and extent of such changes? Can they be turned on and off? |
commented Apr 10, 2018
Its either a manifest edit (thus 'permanent') or an API call so could be changed in a close/open cycle but from memory the API call method can occasionally fail crashing the application and manifest would lock us to >= XP |
commented Apr 10, 2018
@craigwi it's not as dramatic as the name implies. Visual Styles is the name used by Microsoft to refer to buttons and native UI elements drawing in the OS's current visual style. Meaning that If your app sticks to native UI controls, which this does, switching to XP's Luna theme will let your app have the Luna controls. Running the app on Windows 10 would let it use the Windows 10's design style. It's nothing the app has to do. Windows will handle all the work. But because Microsoft's commitment to backwards compatibility, Windows doesn't proactively apply the visual style for apps built using APIs predating Windows XP as to not create potential compatibility issues. All we have to do is let Windows know that we are aware of visual styles, and Windows 10 will draw the buttons, text boxes, and other UI elements in the default Windows 10 UI elements rather than the Windows classic theme, as it's doing now. |
commented Apr 11, 2018
According to the MSDN documentation, all we need to do is call the common controls version 6 dll rather than version 5 through an app manifest. Their sample only shows C++. Do you think this would work in C? Here's the MSDN article: https://msdn.microsoft.com/en-us/library/windows/desktop/bb773175(v=vs.85).aspx#using_manifests |
commented Apr 11, 2018
@NazmusLabs yes it works - see my screenshots above. |
commented Apr 11, 2018
The #pragma works fine. I just copied the exact text from the article and recompiled. However, I do wonder about the section 'Making Your Application Compatible with Earlier Versions of Windows'. I'm ok with this change as long as it runs on all of the older Windows without hassle. Can someone check? |
commented Apr 11, 2018
@craigwi how far back? |
commented Apr 11, 2018
Win7 for sure; XP as a bonus! |
commented Apr 11, 2018
Visual Styles was introduced in XP so it'll work |
commented Apr 11, 2018
@craigwi just took a read of that section. There are two parts. One is for versions of Windows prior to visual styles. That would be Windows 2000 or earlier. And the other part is to test the apps on High Contrast mode both in Windows 7 and in Windows 8 or 10. Windows 8 introduces a new high contrast infrastructure. So we would need to test it on the new and the old system. Testing high contrast on Windows 10 covers 8 and 8.1. Testing on Windiws 7 covers XP and Vista as well. We definitely do need to test the high contrast settings to ensure the application doesn't break. But I am not sure if we need to test Windows 2000 or NT4... I mean I don't have any VMs in hand for those early NT version. I only have a 9x and 3x VM, and WinFile doesn't work on 9x or 3x, as verified by someone in another thread. |
commented Apr 11, 2018
For Windows Server, I think we should target the first version with Visual Styles. Would that be Server 2003 or 2003 R2? |
commented Apr 12, 2018
@craigwi Windows Server 2003 (R1) had visual styles, yes, as it was branched of the Windows XP RC codebase which had visual styles support. So the original server would work as well. |
commented Apr 14, 2018
@Azarien opened PR #92. I am fine with enabling Visual Styles and have verified, at least on Windows 10, that high contrast mode works. @daniel-white, @NazmusLabs, who should get the credit for the fix? |
commented Apr 14, 2018
@craigwi I'd credit @daniel-white since they were the first to discover the relevant MSDN docs and to have the feature implemented. Of course, you also Implemented and verified it working, including in high contrast, which is important. If anyone has an active machine running Windows 7 or older, it's crucial to text the app on high contrast as well as in the windows classic theme. Otherwise, I have an archived Server 2008R2 VM that I can fire up, if need be. |
commented Apr 15, 2018
I have access to 7 if someone can provide an exe of that branch |
commented Apr 15, 2018
@craigwi I'd give credit to @Azarien. he did the actual work to get a PR in. |
commented Apr 16, 2018
I merged @Azarien's change PR #92. |
closed this Apr 16, 2018
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
RECOMMENDED: Click here to fix Windows errors and improve PC performance
If your Windows 10 is running slowly, you can do many things to speed up the operating system. One of the ways is to free up some system resources. You can reduce the system resource usage by closing applications that are not important to you right now, background services, and visual effects.
Like its predecessors, Windows 10 also offers many visual effects, and Windows enables most of them by default. Window animations, shadows under mouse pointer, aero peek, drop shadows for icon labels on desktop, animations in taskbar, and shadows under windows are visual effects.
Visual effects take a considerable amount of system resources and can slow down your Windows 10 PC, especially if your PC has a smaller amount of RAM (4GB or less).
So, if your Windows 10 is running slow, you can disable visual effects to improve the performance. Depending on the amount of RAM on your PC, disabling visual effects might make negligible to significant impact on Windows 10’s performance.
Disabling all Windows 10 visual effects or disabling specific visual effects is easy. You don’t need to edit Registry or system files to disable visual effects.
Disable visual effects in Windows 10 to improve performance
Here is how to disable Windows 10 visual effects to adjust Windows 10 for best performance.
Tip: Did you know that by switching to SSD, you can increase PC’s performance by up to 50%?
Step 1: In the Start/taskbar search field, type Sysdm.cpl and then press Enter key to open System Properties dialog.
Step 2: Switch to the Advanced tab. In the Performance section, click Settings button. You should now see Performance options dialog.
Step 3: Here, choose Adjust for best performance if you want to turn off all visual effects and gain the best possible system performance. Finally, click Apply button.
But if you want to keep certain visual effects, select Custom option, deselect visual effects that you don’t want to see and then click Apply.
WARNING: When visual effects are turned off, fonts on your PC might look odd. If you want to restore the original look of fonts, select Smooth edges of screen fonts, and click Apply.