|
|
Post by s34642542 on Dec 26, 2023 7:09:41 GMT -8
You are doing the Lord's work, my friend. Merry Christmas and thanks for all your amazing mods.
The snapping overspill thing I described is still happening for me (when you de- then re-snap it to the same part, it fixes it, as before), but Task Manager, Device Manager, and Task Scheduler are all now behaving as they should.
Fixed in the latest release, at the expense of it permanently enabling classic theme frames on that window and giving windows a maximum size of 99999x99999 pixels. I really tried to find a good approach to get this working, but I settled for a hack after a few hours of searching.
For some reason, it only breaks if you clear the region too. If you change the region or never touch it, then it works fine, which is how this hack works. I just set a very huge clipping mask on the window if it's not maximised, which fixes the weird positioning bug that Aero Snap has when you snap the window immediately after maximisation.
It's working perfectly now. Thanks again.
On a somewhat related note, any idea why snapping doesn't work properly with the classic theme on? Normally on Windows 10, when you snap something to the side of the screen, it lets you choose another window to snap alongside it. With the classic theme on, this doesn't happen at all. I seem to recall it working just fine on Windows 11 with the classic theme on, but could be misremembering.
|
|
AnyKey
Sophomore Member
Posts: 248
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Dec 26, 2023 10:44:47 GMT -8
All addressed problems should be fixed in version 2.0 of Classic Maximized Windows Fix: - gameinputsvc.exe is now excluded by default
- Compatibility with the classic Task Manager has been improved
- The hooking approach as a whole has been changed, which should improve the UX
Confirmed working at my end. Thank you for working on it. |
|
|
|
Post by ephemeralViolette on Dec 26, 2023 15:06:35 GMT -8
Fixed in the latest release, at the expense of it permanently enabling classic theme frames on that window and giving windows a maximum size of 99999x99999 pixels. I really tried to find a good approach to get this working, but I settled for a hack after a few hours of searching.
For some reason, it only breaks if you clear the region too. If you change the region or never touch it, then it works fine, which is how this hack works. I just set a very huge clipping mask on the window if it's not maximised, which fixes the weird positioning bug that Aero Snap has when you snap the window immediately after maximisation.
It's working perfectly now. Thanks again.
On a somewhat related note, any idea why snapping doesn't work properly with the classic theme on? Normally on Windows 10, when you snap something to the side of the screen, it lets you choose another window to snap alongside it. With the classic theme on, this doesn't happen at all. I seem to recall it working just fine on Windows 11 with the classic theme on, but could be misremembering.
That part's controlled by the shell, and it looks like it may be something like XAML, so it's probably one of those parts of explorer that breaks when explorer can't load themes. I had the snapping menu working fine during testing since I never restarted explorer after starting ClassicThemeTray.
|
|
vindasal
Freshman Member
Posts: 73
OS: Windows 10 Pro 22H2
Theme: XP Luna/Classic depending on mood
|
Post by vindasal on Jan 6, 2024 0:41:31 GMT -8
I'm using a couple Windhawk scripts to fix up the Classic theme, but there's one issue I've found so far. When right clicking in the default Explorer sidebar the context menu is still broken. I'm curious if this is a known issue or a problem caused by the combination of fixes I have applied.
Here's my current scripts:
Here's the issue: |
|
Zul
New Member
Posts: 7 
OS: Windows 10 IoT Enterprise LTSC 2021
Theme: Windows 7
CPU: Intel Celeron N2807
RAM: 4 GB
|
Post by Zul on Jan 6, 2024 1:24:21 GMT -8
I'm using a couple Windhawk scripts to fix up the Classic theme, but there's one issue I've found so far. When right clicking in the default Explorer sidebar the context menu is still broken. I'm curious if this is a known issue or a problem caused by the combination of fixes I have applied.
Here's my current scripts:
Here's the issue: You can use Eradicate Immersive Menus mod, it will fix context nenu systemwide in classic theme.  |
|
|
|
Post by anixx on Jan 6, 2024 4:42:46 GMT -8
Second link in the OP is broken now.
|
|
waldemar21214
Freshman Member
Posts: 94
OS: Windows 10
Theme: Classic
CPU: i5-12400f
RAM: 16 GB DDR4 3600mhz
GPU: PNY 3060TI
|
Post by waldemar21214 on Jan 6, 2024 10:39:04 GMT -8
|
|
AnyKey
Sophomore Member
Posts: 248
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Mar 2, 2024 2:43:08 GMT -8
About Maximized Windows Fix mod. How about removing exclusion for ApplicationFrameHost.exe ? Since UWP apps can now have native title bar and borders. Or injecting into ApplicationFrameHost.exe triggers another issue? And the edges of other monitors spill over when you try to take a screenshot of maximized window (take a look at right edge of the screenshot). Is this fixable? |
|
|
|
Post by ephemeralViolette on Mar 2, 2024 11:45:28 GMT -8
About Maximized Windows Fix mod. How about removing exclusion for ApplicationFrameHost.exe ? Since UWP apps can now have native title bar and borders. Or injecting into ApplicationFrameHost.exe triggers another issue? And the edges of other monitors spill over when you try to take a screenshot of maximized window (take a look at right edge of the screenshot). Is this fixable? I haven't tried injecting into ApplicationFrameHost, but I think it shouldn't be too problematic if combined with native titlebar UWP applications. Have you tried enabling it manually?
I'll have to look into the screenshot spilling over thing. I never realised this problem, but hopefully it's not too difficult to fix.
|
|
AnyKey
Sophomore Member
Posts: 248
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Mar 4, 2024 9:03:26 GMT -8
I haven't tried injecting into ApplicationFrameHost, but I think it shouldn't be too problematic if combined with native titlebar UWP applications. Have you tried enabling it manually? I tried manually injecting into ApplicationFrameHost and I didn't see any issues (at least for me). |
|
konstidog
Freshman Member
Posts: 33
OS: Windows 10 22H2
Theme: Windows Vista babeeey
CPU: AMD Ryzen 9 5900X
RAM: 64GB DDR4 G-Skill Trident Z
GPU: Sapphrie RX 570 4GB
|
Post by konstidog on Apr 14, 2024 4:50:47 GMT -8
Icon Resource Redirect by m417z windhawk.net/mods/icon-resource-redirectThis one is huge! Just got submitted the other day. Could replace 7TSP for icon modding.
Explorer.exe resources are also changeable! 🥳
![]() |
|
Jevil7452
Regular Member
Posts: 434
OS: Windows 7 Enterprise (6.1.7601)
Theme: Windows Aero by Microsoft Corporation
CPU: Intel Core i7-3770k
RAM: 32GB (4x8GB DDR3)
GPU: NVIDIA GeForce GTX 980 Ti + Intel(R) HD Graphics 4000
Computer Make/Model: OEM0
|
Post by Jevil7452 on Apr 14, 2024 5:02:29 GMT -8
It could only replace 7TSP if you really insist for it to do so. Resources have always been moddable with Resource Hacker, and modding them yourself is a better way than hooking into every program to change the DLL they're loaded from. Explorer.exe resources were always changeable, you just had to inject them into the .mui file. User32.dll resources still aren't changeable with it. Stuff like shell32.dll, setupapi.dll also work with the MUI trick, or if you don't care about anticheats, just unsign them and boot with no integrity checks.
|
|
konstidog
Freshman Member
Posts: 33
OS: Windows 10 22H2
Theme: Windows Vista babeeey
CPU: AMD Ryzen 9 5900X
RAM: 64GB DDR4 G-Skill Trident Z
GPU: Sapphrie RX 570 4GB
|
Post by konstidog on Apr 14, 2024 5:13:40 GMT -8
I was moreso thinking of the ability to replace these this way with less chance of Windows Update screwing with em tbh.
(inb4 you tell me there was a way of circumventing that already without disabling said updates)
|
|
Jevil7452
Regular Member
Posts: 434
OS: Windows 7 Enterprise (6.1.7601)
Theme: Windows Aero by Microsoft Corporation
CPU: Intel Core i7-3770k
RAM: 32GB (4x8GB DDR3)
GPU: NVIDIA GeForce GTX 980 Ti + Intel(R) HD Graphics 4000
Computer Make/Model: OEM0
|
Post by Jevil7452 on Apr 14, 2024 6:02:45 GMT -8
MUN files do not get replaced with updates for the most part. But still I personally believe that updating modded Windows is a bad idea.
|
|
konstidog
Freshman Member
Posts: 33
OS: Windows 10 22H2
Theme: Windows Vista babeeey
CPU: AMD Ryzen 9 5900X
RAM: 64GB DDR4 G-Skill Trident Z
GPU: Sapphrie RX 570 4GB
|
Post by konstidog on Apr 14, 2024 6:52:36 GMT -8
MUN files do not get replaced with updates for the most part. But still I personally believe that updating modded Windows is a bad idea. Wild bc on my personal 22H2 install, I modded imageres+shell32+other .mun's in SystemResources and they'd frequently get reverted to Win10 icon resources. :\
I wanna give this a test spin to see how it acts between updates. Only part it seems to not catch so far is the shellstyle sidebar element Aero10 adds in.
|
|
|
|
Post by The Jackal on Jul 12, 2024 16:02:00 GMT -8
The new mod "UXTheme hook", does that allow you to change themes without having to patch your system? Is it really as simple as that?
|
|
Jevil7452
Regular Member
Posts: 434
OS: Windows 7 Enterprise (6.1.7601)
Theme: Windows Aero by Microsoft Corporation
CPU: Intel Core i7-3770k
RAM: 32GB (4x8GB DDR3)
GPU: NVIDIA GeForce GTX 980 Ti + Intel(R) HD Graphics 4000
Computer Make/Model: OEM0
|
Post by Jevil7452 on Jul 13, 2024 2:24:01 GMT -8
Apparently yeah, though personally I don't see the point of it over UltraUxThemePatcher (or SecureUxTheme if you don't want to modify system files)
|
|
|
|
Post by The Jackal on Jul 13, 2024 13:29:31 GMT -8
Apparently yeah, though personally I don't see the point of it over UltraUxThemePatcher (or SecureUxTheme if you don't want to modify system files) Thank you for answering my question. |
|
