|
|
Post by powerplayer on Oct 7, 2018 16:24:01 GMT -8
can i have your method please?
|
|
|
|
Post by anixx on Oct 8, 2018 2:38:14 GMT -8
how did you fix that Splitwirez? Technically I didn't fix anything. We're just rewriting it... There is no ClientEdge on your screenshots. |
|
|
|
Post by prozad93 on Oct 16, 2018 0:35:53 GMT -8
yikes that is such a shame how they managed to mess up everything just to make it more difficult for us.
|
|
|
|
Post by antiufo on Nov 24, 2018 2:26:19 GMT -8
AFAIK, the resources used by the classic theme are stored in the Marlett.ttf font. However, expand/collapse don't seem to be there (but this was also the case with previous Windows version). Perhaps they're drawn programmatically (after all, they're just horizontal/vertical lines).
|
|
|
|
Post by 6sicsix on Nov 27, 2018 3:15:38 GMT -8
You're probably right - i assume they were not actually removed as the same icons seem to be used in mmc / device manager
i'm using ltsb 2016 now (with the store re-added)
If splitwirez could go into some detail about how to get around the missing shellstyle.dll that would be great.
There are lots of vague answers and references to start9 (which isn't available yet?)
|
|
|
|
Post by powerplayer on Nov 27, 2018 20:50:12 GMT -8
If splitwirez could go into some detail about how to get around the missing shellstyle.dll that would be great. There are lots of vague answers and references to start9 (which isn't available yet?) I second that one. Because start9 will take ages why not make a classicthemea.exe kinda thing for a stripped version of start9 thats only for handling windows that runs like a service and replaces classic explorer open windows. |
|
