|
|
Post by OrthodoxWin32 on Mar 1, 2022 17:33:51 GMT -8
You're spreading misinformation. SCT and SCTT support x86. SCT does not support ExplorerPatcher on Windows 10. And ExplorerPatcher is not the only taskbar inside SCT, there's 4 others. What ? I said only that Explorerpacher is the only correct solution for the context menu.
I do not say that ExplorerPatcher was the only solution for the taskbar.
In addition, I recognized that my proposal to explore patcher for the taskbar was irrelevant.
|
|
|
|
Post by leet on Mar 2, 2022 1:29:50 GMT -8
You're spreading misinformation. SCT and SCTT support x86. SCT does not support ExplorerPatcher on Windows 10. And ExplorerPatcher is not the only taskbar inside SCT, there's 4 others. What ? I said only that Explorerpacher is the only correct solution for the context menu.
I do not say that ExplorerPatcher was the only solution for the taskbar.
In addition, I recognized that my proposal to explore patcher for the taskbar was irrelevant.
Still misinformation, ECMT has been around for years now and although it is not the best solution, it is currently the only SCT supported one. I ask you to stop providing people with information you don’t know about in a thread where people want legit help with getting SCT working. |
|
|
|
Post by OrthodoxWin32 on Mar 2, 2022 2:57:10 GMT -8
What ? I said only that Explorerpacher is the only correct solution for the context menu.
I do not say that ExplorerPatcher was the only solution for the taskbar.
In addition, I recognized that my proposal to explore patcher for the taskbar was irrelevant.
Still misinformation, ECMT has been around for years now and although it is not the best solution, it is currently the only SCT supported one. I ask you to stop providing people with information you don’t know about in a thread where people want legit help with getting SCT working.
Regarding the problem of contextual menus, it turns out that the question that Nonameneeded had posed did not concern the good topic; It is therefore logical that my answer is off-topic. In addition, I find it surprising that ECMT is still a topic, while this software does work clearly not properly, and the similar function of EP is incomparable. I find dishonest to redirect users to an unreliable solution. And again, the problem was not my answer, but the question posed about the context menus that had nothing to do with SCT. Anyway, I'm not about going back to SCT topic. |
|
|
|
Post by leet on Mar 25, 2022 8:56:40 GMT -8
In addition, I find it surprising that ECMT is still a topic, while this software does work clearly not properly, and the similar function of EP is incomparable. I find dishonest to redirect users to an unreliable solution. And again, the problem was not my answer, but the question posed about the context menus that had nothing to do with SCT. I've been gone for a while, but I still want to comment on this. I definitely get your point about ECMT not being a reliable solution. But it has been the SCT supported solution for literally years and is the only one I have fully implemented into SCT. ExplorerPatcher has been a recent development in the community, and although I have added support for it, I haven't fully made use of all it's capabilities for use within SCT yet. One of those capabilities is the context menu's. I specifically mentioned ECMT because installing EP and SCT separately on Windows 10 can cause issues regarding the taskbar, as SCT doesn't know it's present. And the problem was actually your answer. The question was regarding an issue that comes up when using Classic Theme through SCT. Considering the user asked it here, it's safe to assume they're using SCT. So that leaves only one possible option for fixing their issue: ECMT. One final comment regarding when there will be Win10 support for SCT+EP: I really don't know. I have been busy with other stuff lately, and haven't had much motivation to get back into Classic. When I do, I will happily integrate EP's full capabilities within SCT. |
|
|
|
Post by OrthodoxWin32 on Mar 26, 2022 3:25:14 GMT -8
I've been gone for a while, but I still want to comment on this. I definitely get your point about ECMT not being a reliable solution. But it has been the SCT supported solution for literally years and is the only one I have fully implemented into SCT. ExplorerPatcher has been a recent development in the community, and although I have added support for it, I haven't fully made use of all it's capabilities for use within SCT yet. One of those capabilities is the context menu's. I specifically mentioned ECMT because installing EP and SCT separately on Windows 10 can cause issues regarding the taskbar, as SCT doesn't know it's present. And the problem was actually your answer. The question was regarding an issue that comes up when using Classic Theme through SCT. Considering the user asked it here, it's safe to assume they're using SCT. So that leaves only one possible option for fixing their issue: ECMT. One final comment regarding when there will be Win10 support for SCT+EP: I really don't know. I have been busy with other stuff lately, and haven't had much motivation to get back into Classic. When I do, I will happily integrate EP's full capabilities within SCT. I understand better now. Indeed, from this angle, my answer was irrelevant. For SCT + EP support, it is possible that the problem with the taskbar is linked to the advanced mitigation for classic theme option. It is possible that if this option is disabled, EP is SCT compatible. I would test this soon (I do not use SCT regularly). Apart from that, I think it would be nice to make a comparative table of classic taskbar solutions, with the features and especially the common compatibility and problems (and the means of resold them), because I have the sensation that many users are a little lost with the different possibilities. I would take care of it for me to have time. |
|
|
|
Post by ayylmao on Mar 26, 2022 4:49:03 GMT -8
I've been gone for a while, but I still want to comment on this. I definitely get your point about ECMT not being a reliable solution. But it has been the SCT supported solution for literally years and is the only one I have fully implemented into SCT. ExplorerPatcher has been a recent development in the community, and although I have added support for it, I haven't fully made use of all it's capabilities for use within SCT yet. One of those capabilities is the context menu's. I specifically mentioned ECMT because installing EP and SCT separately on Windows 10 can cause issues regarding the taskbar, as SCT doesn't know it's present. And the problem was actually your answer. The question was regarding an issue that comes up when using Classic Theme through SCT. Considering the user asked it here, it's safe to assume they're using SCT. So that leaves only one possible option for fixing their issue: ECMT. One final comment regarding when there will be Win10 support for SCT+EP: I really don't know. I have been busy with other stuff lately, and haven't had much motivation to get back into Classic. When I do, I will happily integrate EP's full capabilities within SCT. I understand better now. Indeed, from this angle, my answer was irrelevant. For SCT + EP support, it is possible that the problem with the taskbar is linked to the advanced mitigation for classic theme option. It is possible that if this option is disabled, EP is SCT compatible. I would test this soon (I do not use SCT regularly). Apart from that, I think it would be nice to make a comparative table of classic taskbar solutions, with the features and especially the common compatibility and problems (and the means of resold them), because I have the sensation that many users are a little lost with the different possibilities. I would take care of it for me to have time. For what its worth I tried and this did not help me. I am not certain what causes the crashing and the incompatibility with EP/ECMT but for some reason any file's context menu can be access harmlessly from the file menu on the top of explorer windows. I don't really consider this a work around though because I could already cheat with everything.exe to do that. I am more focused on trying to keep the configuration from exploding, and accidentally right clicking something because I've done it hundreds of thousands of times before is too much muscle memory to fight. |
|
|
|
Post by leet on Apr 13, 2022 12:51:48 GMT -8
I'm currently working on a new system of implementing classic theme. It uses the themesection method at its core, but builds on top of that with a system service. This allows it to:
not have a admin application run on boot, only the service which can be protected in a similar way as system files.
not require .NET 4.8, or any version for that matter.
work on standard (non-admin) users.
be configured for multiple users.
run on boot with multiple users.
Right now it works under specific circumstances only due to me not knowing how ACL's work, but when I fix that it can be further developed into an application.
|
|
|
|
Post by OrthodoxWin32 on Apr 13, 2022 14:04:07 GMT -8
I'm currently working on a new system of implementing classic theme. It uses the themesection method at its core, but builds on top of that with a system service. This allows it to: not have a admin application run on boot, only the service which can be protected in a similar way as system files. not require .NET 4.8, or any version for that matter. work on standard (non-admin) users. be configured for multiple users. run on boot with multiple users. Right now it works under specific circumstances only due to me not knowing how ACL's work, but when I fix that it can be further developed into an application. This looks very interesting, including the ability to configure the classic theme in a multi-user environment. Good luck for development ! |
|
|
|
Post by leet on Apr 16, 2022 14:17:37 GMT -8
Here's a little look at it working in action: youtu.be/uG5x3tiFmeAThis doesn't showcase the multi-user part because, A: I haven't made it yet and B: it's hard to show that in a video. |
|
|
|
Post by leet on Apr 17, 2022 13:54:02 GMT -8
Here's a diagram on how MCT (Multi-user Classic Theme) works. It's a simple architecture, but it allows for all of the earlier mentioned benefits:  |
|
|
|
Post by leet on Apr 30, 2022 15:13:50 GMT -8
sneak peak:  sct 1.7.0 will contain this, mct, and it will be the most stable version of sct yet. |
|
|
|
Post by friend on May 30, 2022 17:37:48 GMT -8
Hey Leet many thanks for this program. It's unfortunate that it uses .Crap Framework, and a recent version at that. So I'm compelled to install more M$ bloat to run this tool. This happens if I don't have it:  This application might as well have been developed using .NET 2.0. I just changed the "Target Framework" option in VS to 4.0 and the only errors I got when trying to build it were related to recent syntactic handicappings of that language:  These are the only characteristics of BotNet Core used in this application. Changing to .Crap version 4.7.2 makes it run successfully. So there is no reason to use the Latest Version™, not even a slightly older one, except for syntactic stupidities such as inline functions, or whatever term is used for them, and tuples:   By using that all users are required to add bloat to their systems. The .Crap Runtime requires:  Had it a lower target framework this would not be necessary. Or, even better, had it been developed using a more tasteful language, no extra dependencies would be necessary. Thank you very much for your work.  |
|
|
|
Post by leet on May 31, 2022 0:15:38 GMT -8
friend You're mixing up two pieces of software here: SCT and SCT Taskbar. SCT only requires .NET Framework 4.8, which is preinstalled on Windows 10. SCT Taskbar, a separate program that acts as a replacement for the windows taskbar, requires .NET Desktop Runtime 5.0. Fun fact: Both SCT and SCTT at the start used .NET 4.7.2. I migrated SCT to 4.8 because I wanted to use value tuples, and Windows 10 supports it out of the box anyways. SCT Taskbar was migrated because of a more important reason: .NET 5.0 is much much faster than any version of .NET Framework. I was running into performance issues with SCTT on .NET 4.7.2 and migrating to the newer framework partially resolved that. The fact that users will need to install the framework was a compromise I was willing to take because it made the program more usable on lower-end systems. I wasn't going to migrate SCT to .NET 4.7.2, but in SCT 1.7.0 I coincidentally removed the unsupported code (quality issues) and thus lowered it back to .NET 4.7.2. But it shouldn't make a difference anyway, as .NET 4.8 is preinstalled on any version of Windows 10 or 11. SCT Taskbar won't be migrated as development on it has been ceized. There may or may not be a native replacement in the works. One more thing: the .NET 5.0 Desktop Runtime shouldn't be 730MB. IIRC it's only about 250MB, so the screenshots you showed are probably multiple versions of .NET.
|
|
|
|
Post by leet on May 31, 2022 0:19:37 GMT -8
> Had it a lower target framework this would not be necessary. Or, even better, had it been developed using a more tasteful language, no extra dependencies would be necessary.
I quickly want to add about this: Yes this is true, but you can't just tell any developer: you should use this or this. It takes time and effort to learn and understand the syntax of a language and the underlying frameworks. I did C# with .NET because I know it very well and can code in it quickly.
|
|
|
|
Post by friend on May 31, 2022 2:44:32 GMT -8
<abbr>Right, I was talking about the Taskbar. The other part works fine for me, without need to install additional garbage. </abbr> Yeah just came to mind how much crap software there is out there nowadays, and BotNetFramework has become part of that. Considering that low-level applications, that use WinAPI directly, have graphics rendering, &c. would only benefit from non-bloated non-dumb languages. Then again, considering that the target system is M$ Windows 10 etc., bloat is a natural thing. Forgive the tone. I used to really like C# until around 2012, after that time, that language, BotNetFramework and related stuff only went downhill. Hate bloat, dumb languages, """modern""" software and what kids call programming nowadays. A small bug I've found in SCT, is that if you cannot connect to the Internet, the program would either hang or just close with no error at some point during installation. I will not join Sh*tHub. Many thanks Leet, this is good stuff.  |
|
Ofelia
Freshman Member
(─‿‿─)
Posts: 53 
OS: Windows binary code
Theme: I don't even know
CPU: a microwaved potato
RAM: 16GB potato PC
GPU: another microwaved potato
|
Post by Ofelia on May 31, 2022 15:57:04 GMT -8
Average StackOverflow user : <abbr>Right, I was talking about the Taskbar. The other part works fine for me, without need to install additional garbage. </abbr> Yeah just came to mind how much crap software there is out there nowadays, and BotNetFramework has become part of that. Considering that low-level applications, that use WinAPI directly, have graphics rendering, &c. would only benefit from non-bloated non-dumb languages. Then again, considering that the target system is M$ Windows 10 etc., bloat is a natural thing. Forgive the tone. I used to really like C# until around 2012, after that time, that language, BotNetFramework and related stuff only went downhill. Hate bloat, dumb languages, """modern""" software and what kids call programming nowadays. A small bug I've found in SCT, is that if you cannot connect to the Internet, the program would either hang or just close with no error at some point during installation. I will not join Sh*tHub. Many thanks Leet, this is good stuff.  |
|
|
|
Post by friend on May 31, 2022 23:48:36 GMT -8
Average StackOverflow user : Why is that, friend? I don't understand. I hate ShekelExchange, ShekelOverflow included; they are part of the cause why things are as they are nowadays regarding computer programs. Filled to the brim with dumb software and languages. Insufferable users from top to bottom. The websites themselves are dumbed-down J*vaScript-laden piles of dung. |
|
|
|
Post by anixx on Jun 1, 2022 3:06:01 GMT -8
sneak peak: sct 1.7.0 will contain this, mct, and it will be the most stable version of sct yet. From this screenshot I see that it does not show the chess-like pattern on the scrollbar. This is the default Win2000 scheme, so the scrollbar should be chess-patterned.  There are two different colors involved. |
|
|
|
Post by leet on Jun 1, 2022 3:20:58 GMT -8
The scrollbars in the preview are disabled scrollbars. Those do not use a gradient, rather they're just the darker color spread out over the full scrollbar area.
|
|
|
|
Post by leet on Jun 2, 2022 5:39:43 GMT -8
The scrollbars in the preview are disabled scrollbars. Those do not use a gradient, rather they're just the darker color spread out over the full scrollbar area. I am incorrect about this. Even disabled scrollbars display a checkerboard pattern, my bad. |
|
