|
|
Post by Splitwirez on Dec 8, 2016 9:25:00 GMT -8
|
|
|
|
Post by powerplayer on Dec 8, 2016 18:03:42 GMT -8
is it not possible to use reshacker to replace those buttons anyway?
|
|
|
|
Post by Splitwirez on Dec 8, 2016 19:02:29 GMT -8
is it not possible to use reshacker to replace those buttons anyway? Well, yes, you can replace the glyphs...but not the entire button. Nor can you change the sizes of the buttons, nor add a titlebar, nor change the position of the titlebar text, nor alter the coloured background or how the icon is displayed...long story short, 90% of what I'm suggesting here can't be done via simple Reshacking. Oh and even if it could, good luck getting that to match system colours. (Also, need I mention once more that UWP Apps don't even consistently work on Windows 10 with the Classic Theme? .-. ) |
|
|
|
Post by rancorx2 on Mar 5, 2018 1:35:13 GMT -8
aren't a lot of the resources stored in those annoying pri files? (which we can't edit, well you can if you dump them using makepri but then you can't convert them back to pri without the source files afaik)
isn't the theme thing because they are sandboxed? separate from the win32 stuff?
|
|
|
|
Post by Splitwirez on Mar 5, 2018 12:17:45 GMT -8
aren't a lot of the resources stored in those annoying pri files? (which we can't edit, well you can if you dump them using makepri but then you can't convert them back to pri without the source files afaik) Close...from my research, I've learned that evidently the resources themselves are loose in the App's folder, but the name mappings, and by extension, things like different variants for High Contrast mode and such, are stored in the pri files. That having been said, this was on Windows 8.1, things may have changed since then (although I kinda doubt they would). isn't the theme thing because they are sandboxed? separate from the win32 stuff? Err...technically no, MS easily could've used MsStyles-based titlebars (just look at ModernMix, AeroGlass 8.1+'s ModernFrame.dll, or the earliest Technical Preview builds of Windows 10). Buuut they didn't, hence the obstacles we now face. |
|
