aubymori
Sophomore Member
👅👅👅👅👅
Posts: 160 
OS: Windows 10 IoT Enterprise LTSC 2021
Theme: Windows 10 Default
CPU: Intel Core i5-9300H
RAM: 8GB
GPU: Intel UHD Graphics 630 / NVIDIA GeForce GTX 1650
|
Post by aubymori on Oct 30, 2023 15:57:50 GMT -8
The DWM dialogs still use non-classic buttons despite the window border is fixed by "non-responsive" mod: How exactly do you trigger this? |
|
|
|
Post by anixx on Oct 30, 2023 19:36:29 GMT -8
The DWM dialogs still use non-classic buttons despite the window border is fixed by "non-responsive" mod: How exactly do you trigger this? What exactly? |
|
aubymori
Sophomore Member
👅👅👅👅👅
Posts: 160
OS: Windows 10 IoT Enterprise LTSC 2021
Theme: Windows 10 Default
CPU: Intel Core i5-9300H
RAM: 8GB
GPU: Intel UHD Graphics 630 / NVIDIA GeForce GTX 1650
|
Post by aubymori on Oct 31, 2023 17:59:11 GMT -8
How exactly do you trigger this? What exactly? The dialog in the screenshot. |
|
|
|
Post by anixx on Nov 1, 2023 0:07:30 GMT -8
Using DWM ghost mod by Abymori
|
|
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 Nov 7, 2023 4:17:18 GMT -8
Late to say this but another issue of Maximized Windows mod.
This mod slows down the computer for some reason.
Especially, the task manager slows down over time and becomes late to respond.
|
|
|
|
Post by The Jackal on Nov 12, 2023 12:07:48 GMT -8
The DWM Ghost mod stopped working when I upgraded to Windhawk 1.4.
|
|
|
|
Post by ephemeralViolette on Nov 12, 2023 12:12:33 GMT -8
The DWM Ghost mod stopped working when I upgraded to Windhawk 1.4. Ah, I haven't tested Windhawk 1.4 at all. Have you tried either recompiling it under 1.4 or compiling it under 1.3 and then upgrading to 1.4?
|
|
|
|
Post by The Jackal on Nov 12, 2023 14:04:21 GMT -8
The DWM Ghost mod stopped working when I upgraded to Windhawk 1.4. Ah, I haven't tested Windhawk 1.4 at all. Have you tried either recompiling it under 1.4 or compiling it under 1.3 and then upgrading to 1.4?
I just tried both and sadly I can't get it to work. It works fine under 1.3, but it doesn't like 1.4 for me. |
|
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 Nov 12, 2023 18:20:46 GMT -8
The DWM Ghost mod stopped working when I upgraded to Windhawk 1.4. The update might have reset your critical system processes injection setting. Try checking it out. |
|
|
|
Post by The Jackal on Nov 13, 2023 5:00:20 GMT -8
The DWM Ghost mod stopped working when I upgraded to Windhawk 1.4. The update might have reset your critical system processes injection setting. Try checking it out. Still nothing, sorry. |
|
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 Nov 13, 2023 5:58:42 GMT -8
The DWM Ghost mod stopped working when I upgraded to Windhawk 1.4. I deleted the value <critical_system_processes> in Process exclusion list section under More advanced settings, leave it blank, and restart Windhawk, and the mods that inject critical process will work again like before. You can try it. |
|
|
|
Post by The Jackal on Nov 13, 2023 6:42:45 GMT -8
The DWM Ghost mod stopped working when I upgraded to Windhawk 1.4. I deleted the value <critical_system_processes> in Process exclusion list section under More advanced settings, leave it blank, and restart Windhawk, and the mods that inject critical process will work again like before. You can try it. I don't think that's a good idea, but I took a look in the settings ini in the AppData/Engine folder anyway, and it turns out for some reason "InjectIntoCriticalProcesses" was set to 0, even though it is turned on via Windhawk itself. I turned it to 1 and the mod now works as it did on 1.3. Sorry ephemeralViolette for mis-reporting the mod as no longer working. |
|
|
|
Post by anixx on Nov 13, 2023 23:33:26 GMT -8
I did not encounter these problems.
|
|
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 Nov 16, 2023 13:27:55 GMT -8
Late to say this but another issue of Maximized Windows mod. This mod slows down the computer for some reason. Especially, the task manager slows down over time and becomes late to respond. Ah, the mod should not be injected into gameinputsvc.exe. Injecting into it triggers this issue. I assumed this was due to conflict with another mod and didn't check other causes at all. I suggest to exclude it (as long as you have it). After I found this out, I haven't experienced another issue with this mod as for now. Sorry for bothering. I appreciate ephemeralViolette's great work again. |
|
|
|
Post by ephemeralViolette on Nov 16, 2023 13:59:35 GMT -8
Late to say this but another issue of Maximized Windows mod. This mod slows down the computer for some reason. Especially, the task manager slows down over time and becomes late to respond. Ah, the mod should not be injected into gameinputsvc.exe. Injecting into it triggers this issue. I assumed this was due to conflict with another mod and didn't check other causes at all. I suggest to exclude it (as long as you have it). After I found this out, I haven't experienced another issue with this mod as for now. Sorry for bothering. I appreciate ephemeralViolette's great work again. I will fix this in the next update. |
|
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 Nov 17, 2023 4:07:25 GMT -8
Ah, the mod should not be injected into gameinputsvc.exe. Injecting into it triggers this issue. I assumed this was due to conflict with another mod and didn't check other causes at all. I suggest to exclude it (as long as you have it). After I found this out, I haven't experienced another issue with this mod as for now. Sorry for bothering. I appreciate ephemeralViolette's great work again. I will fix this in the next update. Thank you again. |
|
|
|
Post by s34642542 on Dec 24, 2023 5:05:54 GMT -8
A few small things about the Maximised Windows mod:
Sometimes if you snap a window to the side of the screen, it will show the border on the second monitor the first time. If you then move the window away and snap it a second time at the same part of the screen, the border overspill will be gone. It seems a bit inconsistent, but it usually happens for me with Firefox windows when I have multiple open at once, and with the classic task manager. This is a very minor thing because re-snapping it fixes the issue, but I thought it was worth highlighting anyway.
I also noticed that the Device Manager and Task Scheduler windows still have border overspill when maximised (but not when snapped)... Well, kind of. It shows a black bar on the second monitor edge, rather than the actual window. Restoring then maximising again doesn't fix this one.
|
|
|
|
Post by ephemeralViolette on Dec 25, 2023 0:03:23 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
|
|
|
|
Post by s34642542 on Dec 25, 2023 7:43:11 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
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.
|
|
|
|
Post by ephemeralViolette on Dec 26, 2023 1:11:35 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
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.
|
|
