|
|
Post by travis on Jan 2, 2023 13:57:14 GMT -8
Removing all properties but imagefile on the "Hot" state will not break the msstyle. Removing it is what causes it to break the theme. I tried that and it just made the selection thing completely white. I decided to try and delete everything, the result being...  This is rather interesting, probably got to be a problem with 1809 being buggy since you use LTSC 2019. Does menupopups look messed up? |
|
Saturn
Sophomore Member
"Windows 10 transformed to Windows 7" more like "Windows 7 Wish.com Edition"
Posts: 137 
OS: Windows 7 Enterprise
Theme: Aero
CPU: Intel Core i5-6200U
RAM: 8GB DDR4
GPU: Intel HD Graphics 520 | NVIDIA GeForce 940MX
|
Post by Saturn on Jan 2, 2023 14:00:01 GMT -8
 Yes, and also the explorer toolbar background is messed up. |
|
|
|
Post by travis on Jan 2, 2023 14:09:55 GMT -8
Shame that it breaks the msstyles, how are those things even related to Desktop::Listview? Could msstyleEditor corrupt the msstyle the same way resource hacker does?
|
|
Saturn
Sophomore Member
"Windows 10 transformed to Windows 7" more like "Windows 7 Wish.com Edition"
Posts: 137
OS: Windows 7 Enterprise
Theme: Aero
CPU: Intel Core i5-6200U
RAM: 8GB DDR4
GPU: Intel HD Graphics 520 | NVIDIA GeForce 940MX
|
Post by Saturn on Jan 2, 2023 14:14:31 GMT -8
I tried to solve this issue by making another imagefile property with the same value (663) and it did not work.
I might try doing this but with WSB, I will give you a DL to it tomorrow.
|
|
|
|
Post by travis on Jan 2, 2023 14:22:46 GMT -8
I tried to solve this issue by making another imagefile property with the same value (663) and it did not work. I might try doing this but with WSB, I will give you a DL to it tomorrow. I just tried doing it with WSB, didn't work at all. Selection on desktop is uneffected. Trying to test the msstyle on msstyleEditor shows a error.
|
|
Saturn
Sophomore Member
"Windows 10 transformed to Windows 7" more like "Windows 7 Wish.com Edition"
Posts: 137
OS: Windows 7 Enterprise
Theme: Aero
CPU: Intel Core i5-6200U
RAM: 8GB DDR4
GPU: Intel HD Graphics 520 | NVIDIA GeForce 940MX
|
Post by Saturn on Jan 2, 2023 14:25:35 GMT -8
I guess we can only give up regarding Desktop::listview then. :(
|
|
|
|
Post by OrthodoxWin32 on Jan 2, 2023 15:53:19 GMT -8
This is because it is probably a common image between different elements. I had this issue with the background of tabs (in property pages) which was tied to the background of menus. Fortunately, all I had to do was change the background of the menus to "BORDERFILL". It may be possible for this case, I'll see.
|
|
|
|
Post by OrthodoxWin32 on Jan 2, 2023 16:10:53 GMT -8
Interesting fact: I toggled the BGTYPEs of the SELECTED and HOTSELECTED sections of Desktop::ListView/LISTITEM to NONE (instead of IMAGEFILE), this crashed the system, with flickering between a black screen and controls with the classic theme. I had to restart the system.
I'm starting to think this has something to do with shellstyle.dll.
|
|
|
|
Post by OrthodoxWin32 on Jan 2, 2023 16:52:50 GMT -8
Obviously, the smelbe crash only occur when changing to NONE from the BGTYPE of the HOTSELECTED section.
Otherwise, I ran into the same problem deleting everything.
It seems that adding even a single element (even if that element has nothing to do with it) makes the problems go away. However, this is enough to display a white selection rectangle on the desktop icons, even for an element that has nothing to do with it.
So it's an internal problem or in the Theme API, or in shellstyle.dll, or both, the problem being the detection or not of the visual style on the elements of the desktop.
I think shellstyle has a fault, because most of the broken stuff is in explorer (address bar, scroll search). Only the menus are broken also outside the explorer.
The broken scrollbar in explorer (it is broken only in explorer) reminds me of the scrollbar of some Windows Whistler test styles (Sample test visual style, Candy).
|
|
Saturn
Sophomore Member
"Windows 10 transformed to Windows 7" more like "Windows 7 Wish.com Edition"
Posts: 137
OS: Windows 7 Enterprise
Theme: Aero
CPU: Intel Core i5-6200U
RAM: 8GB DDR4
GPU: Intel HD Graphics 520 | NVIDIA GeForce 940MX
|
Post by Saturn on Jan 3, 2023 3:00:25 GMT -8
I made my context menus finally clean. Here's a picture before I did changes:  And here's after.  I don't know how to get rid of "Edit file type". |
|
Saturn
Sophomore Member
"Windows 10 transformed to Windows 7" more like "Windows 7 Wish.com Edition"
Posts: 137
OS: Windows 7 Enterprise
Theme: Aero
CPU: Intel Core i5-6200U
RAM: 8GB DDR4
GPU: Intel HD Graphics 520 | NVIDIA GeForce 940MX
|
Post by Saturn on Jan 3, 2023 3:06:18 GMT -8
Interesting fact: I toggled the BGTYPEs of the SELECTED and HOTSELECTED sections of Desktop::ListView/LISTITEM to NONE (instead of IMAGEFILE), this crashed the system, with flickering between a black screen and controls with the classic theme. I had to restart the system. I'm starting to think this has something to do with shellstyle.dll. Nothing bad happens for me when I set it to NONE  |
|
Saturn
Sophomore Member
"Windows 10 transformed to Windows 7" more like "Windows 7 Wish.com Edition"
Posts: 137
OS: Windows 7 Enterprise
Theme: Aero
CPU: Intel Core i5-6200U
RAM: 8GB DDR4
GPU: Intel HD Graphics 520 | NVIDIA GeForce 940MX
|
Post by Saturn on Jan 3, 2023 14:27:45 GMT -8
 By the way I found something strange with Discord (and maybe other Electron applications). I removed everything from listview and it works fine on everything else, but discord insists to use the default Luna10 selection thing. I found out why this happens. Discord refuses to use ListView and instead uses ItemsView. And I did not remove properties from ItemsView, thus this happens. |
|
|
|
Post by OrthodoxWin32 on Jan 3, 2023 15:38:48 GMT -8
I found out why this happens. Discord refuses to use ListView and instead uses ItemsView. And I did not remove properties from ItemsView, thus this happens. This is probably because it is a 32bit program; I tried on software containing both a 32bit version and a 64bit version (VirtualDub): the 32bit version always uses ItemsView, and the 64bit version ListView. Maybe it's related to the Register as a ShellExtension option in ExplorerPatcher, which maybe only hooks 64bit programs ? |
|
zuri
Freshman Member
Posts: 44
OS: Windows 10 1909
Theme: Windows XP Luna
|
Post by zuri on Jan 4, 2023 22:51:54 GMT -8
Can you try to recreate the User Accounts window? Here's a photo of what I mean  |
|
Saturn
Sophomore Member
"Windows 10 transformed to Windows 7" more like "Windows 7 Wish.com Edition"
Posts: 137
OS: Windows 7 Enterprise
Theme: Aero
CPU: Intel Core i5-6200U
RAM: 8GB DDR4
GPU: Intel HD Graphics 520 | NVIDIA GeForce 940MX
|
Post by Saturn on Jan 5, 2023 2:42:46 GMT -8
i probably can, Do not think about it actually working tho
|
|
|
|
Post by travis on Jan 5, 2023 2:58:17 GMT -8
if you follow these for popoup menus, you can remove the left spacing on separators.
|
|
Saturn
Sophomore Member
"Windows 10 transformed to Windows 7" more like "Windows 7 Wish.com Edition"
Posts: 137
OS: Windows 7 Enterprise
Theme: Aero
CPU: Intel Core i5-6200U
RAM: 8GB DDR4
GPU: Intel HD Graphics 520 | NVIDIA GeForce 940MX
|
Post by Saturn on Jan 5, 2023 3:16:47 GMT -8
if you follow these for popoup menus, you can remove the left spacing on separators.
Do I need WSB for this? |
|
|
|
Post by travis on Jan 5, 2023 13:51:52 GMT -8
if you follow these for popoup menus, you can remove the left spacing on separators.
Do I need WSB for this? No, I did it with msstyleEditor.
|
|
|
|
Post by OrthodoxWin32 on Jan 5, 2023 15:58:20 GMT -8
No, I did it with msstyleEditor.
I didn't have time to try today, but it looks like a great find ! |
|
zuri
Freshman Member
Posts: 44
OS: Windows 10 1909
Theme: Windows XP Luna
|
Post by zuri on Jan 5, 2023 18:42:53 GMT -8
If you use AutoHotkey, you can recreate some Windows XP wizards or balloon messages.
|
|
