Going where (official) skinning doesn't allow us to go (on Windows)

[Gruust]

I have set up a theme hack dll project at github:

https://github.com/jjYBdx4IL/ReaperThemeHackDll

Finally, it's possible to adjust Reaper's main menu bar colors.

Use at your own risk. I won't provide binaries, but it's straightforward to build.

[fourdogslong]

Thanks I'll give it a shot if I can figure out how it works.
Btw what theme is that in your screenshot?

[Gruust]

The theme is rLive.

[Gruust]

Maybe the Reaper devs get some idea from that on how simple it could be to add true dark mode support supported by Windows itself. Current status seems to be that widgets need to be owner-drawn (I'm currently stuck on the preset ComboBox above the Juce instrument window), but I read some comments that indicate otherwise - although I haven't found out yet how to make Windows switch them to dark mode. Owner drawn would of course have the advantage that they become skinnable. And it's very easy to draw them. Windows provides a lot of functionality already.



Menu dropdowns and context menus automatically in dark mode:


.

FX list background is now black, too. Also the other menu bars.

Some stuff needs more fixing (incl configuration and similar dialogs). Atm the configuration dialog is not usable via the detours branch.

[Gruust]

New screenshot.

[thevisi0nary]

Appreciate all efforts on this front from anyone so thank you. I'm not very well versed in Windows theming but is this globally applied to the Windows installation or local to just Reaper? (like what windowblinds does)

I was planning on giving this a shot again soon, I've always been afraid to ruin my Windows install which I've heard of happening before and have had minor issues my self.

[Gruust]

This is just meddling with the running Reaper process.

[jinotsuh]

Originally Posted by thevisi0nary

I was planning on giving this a shot again soon, I've always been afraid to ruin my Windows install which I've heard of happening before and have had minor issues my self.

Just do a full disc backup with something like Acronis, and if anything goes wrong, just restore it.

[jinotsuh]

Originally Posted by Gruust

This is just meddling with the running Reaper process.

Keep meddling.

[Justin]

Originally Posted by Gruust

Maybe the Reaper devs get some idea from that on how simple it could be to add true dark mode support supported by Windows itself.

Very cool! "how simple" hah not simple apparently If you want us to look at integrating some of this let us know.

[ANDYZ]

Originally Posted by Justin

Very cool! "how simple" hah not simple apparently If you want us to look at integrating some of this let us know.

+1

[Pink Wool]

Yes please! +1

[SilenceBetweenWords]

+1 please

[fourdogslong]

Originally Posted by Justin

Very cool! "how simple" hah not simple apparently If you want us to look at integrating some of this let us know.

It would be great to have this built in! A lot of us probably don't have the required skills to install this by themselves.
I had a look at it and I don't understand how, I just don't have that kind of knowledge.

[stuman]

Originally Posted by Justin

Very cool! "how simple" hah not simple apparently If you want us to look at integrating some of this let us know.

+1, that would be awesome

[fourdogslong]

Anybody with more knowledge cares to explain to a total noob like myself how to build and install that thing?

[Gruust]

Originally Posted by fourdogslong

Anybody with more knowledge cares to explain to a total noob like myself how to build and install that thing?

Download the sources as a zip file, install Visual Studio (check Desktop C/C++ development) and CMake (choose "put on path for everyone").

Unpack the sources, open native tools command Prompt (press windows key, enter x64 and it should pop up), navigate to the sources, then enter:

cmake -B build
cd build
cmake --build . --config Release

And if you want to debug or fire up Visual Studio:

explorer ReaperThemeHackDll.sln

[Gruust]

Originally Posted by Justin

Very cool! "how simple" hah not simple apparently If you want us to look at integrating some of this let us know.

well, it's a lot simpler if you have the Reaper sources... and the main code is not even 600 lines of code. That's insanely simple.

[akademie]

Well, so, is there anybody who could compile/build the binaries for "us" non-programmers to try this hack, please?

[Justin]

Originally Posted by Gruust

well, it's a lot simpler if you have the Reaper sources... and the main code is not even 600 lines of code. That's insanely simple.

I'll start on a native REAPER implementation, thanks for all of the R&D

[akademie]

Originally Posted by Justin

I'll start on a native REAPER implementation, thanks for all of the R&D

👍 Justin
thanks

[Fergler]

There’s also this, https://rectify11.net

Someone in r/Reaper just used it to dark-mode their setup system wide

https://www.reddit.com/r/Reaper/comm...ent_dark_mode/

[Pink Wool]

Originally Posted by Justin

I'll start on a native REAPER implementation, thanks for all of the R&D

This is amazing news! Woo-hoo!

[stuman]

Originally Posted by Pink Wool

This is amazing news! Woo-hoo!

Wow, indeed!!

[fourdogslong]

Originally Posted by Gruust

Download the sources as a zip file, install Visual Studio (check Desktop C/C++ development) and CMake (choose "put on path for everyone").

Unpack the sources, open native tools command Prompt (press windows key, enter x64 and it should pop up), navigate to the sources, then enter:

cmake -B build
cd build
cmake --build . --config Release

And if you want to debug or fire up Visual Studio:

explorer ReaperThemeHackDll.sln

Thanks I'll give that a shot!

[Alez156]

Originally Posted by Justin

I'll start on a native REAPER implementation, thanks for all of the R&D

I love it!! 🎉🎉🎉

[_Stevie_]

Originally Posted by Justin

I'll start on a native REAPER implementation, thanks for all of the R&D

Thanks Justin!!!!!

[mister happy]

Originally Posted by Justin

I'll start on a native REAPER implementation, thanks for all of the R&D

Please make the dark menu an option. I work in a studio filled with natural sunlight, and one thing I really appreciate about Reaper is that I was able to create a bright, light-colored theme that suits my environment.

I don't like to spend hours in dark rooms with my pupils dilated, so the existing bright menus with black lettering are greatly appreciated.

Thank you!

[akademie]

Originally Posted by mister happy

Please make the dark menu an option. I work in a studio filled with natural sunlight, and one thing I really appreciate about Reaper is that I was able to create a bright, light-colored theme that suits my environment.

I don't like to spend hours in dark rooms with my pupils dilated, so the existing bright menus with black lettering are greatly appreciated.

Thank you!

OPTIONAL, for sure, that's the plan I believe (and hope)

[ArKaDaTa]

Originally Posted by mister happy

Please make the dark menu an option. I work in a studio filled with natural sunlight, and one thing I really appreciate about Reaper is that I was able to create a bright, light-colored theme that suits my environment.

I don't like to spend hours in dark rooms with my pupils dilated, so the existing bright menus with black lettering are greatly appreciated.

Thank you!

I think this would just unlock much needed customization for these UI elements, so you're probably safe in this regard.

Originally Posted by Justin

I'll start on a native REAPER implementation, thanks for all of the R&D

Thanks a lot for looking into this Justin

[Funkybot]

Originally Posted by Justin

I'll start on a native REAPER implementation, thanks for all of the R&D

Who is this person and what have you done with the real Justin? In all seriousness, thanks!

Sounds like I may eventually have to update to Windows 11 but this would be the first real reason to do so.

And of course, thanks to Gruust for getting the ball rolling on this!

[Touristkiller]

Originally Posted by Justin

Very cool! "how simple" hah not simple apparently If you want us to look at integrating some of this let us know.

Yes please Justin +1
Cool that you want to implement this

[Cluke84]

Originally Posted by Justin

I'll start on a native REAPER implementation, thanks for all of the R&D

+1 would be amazing!

Shoutout to Gruust too, great work!

[Gruust]

Originally Posted by Fergler

There’s also this, https://rectify11.net

Someone in r/Reaper just used it to dark-mode their setup system wide

https://www.reddit.com/r/Reaper/comm...ent_dark_mode/

I'd advise against that. That stuff can easily kill your Windows installation.

[fourdogslong]

Originally Posted by Gruust

I'd advise against that. That stuff can easily kill your Windows installation.

I agree, it sure messed my PC pretty good, I was barely able to restore it.

[Gruust]

Originally Posted by Justin

I'll start on a native REAPER implementation, thanks for all of the R&D

Haha, didn't even realize it's you. If that happens, I'll buy the next few versions, too! I know only two DAWs out there that don't annoy me in dark mode. And both are really buggy. How do you guys (?) keep your code base so reliable with all those frequent updates?

[Gruust]

Originally Posted by Justin

I'll start on a native REAPER implementation, thanks for all of the R&D

Ok, so here is the thing: you probably don't want to use undocumented functions. I did more research and the official ones will require you to draw all menu popups yourself. The dark popup menus seem to be a glitch of the undocumented UAH* events... A quick fix could be done for title bars and menu bars, which would be great because that's what's lingering around on the screen all the time. But regarding menu bars you'd lose some accessibility for blind people or so. All other menu popups would need manual drawing it seems. Easy to do quick and dirty in an unofficial dll, but you probably don't want to touch that stuff. Sys*View32 are unfixable. Best you can do is choose colors that somewhat match 'dark' and the unchangeable scroll bars and headers. Or just replace them completely. They don't do much anyway. Or maybe you have an idea to make ÙI elements pluggable, so theme devs can write C/C++ code for them.

Every DAW with proper dark mode support so far doesn't use Win32 stuff it seems. One uses Gtk2. The others just roll their own. Personally, I'd just go 3d accelerated rendering. That's probably most similar on all platforms on the app level once it's set up, and gives total freedom and better UI performance. If you make the UI rendering pluggable, themers/modders might plug in NanoVG (https://github.com/memononen/nanovg), which already brings portability with it.

[lb0]

Could have done with this feature a year ago - after the stupid blindingly white menu bars Windows 10 forces on everyone meant I have Reaper's main menu bar and action list outline permanently burnt into my expensive main ultra super-wide monitor . Since this happened - I used various windows hacks to force everything to dark mode. But these hacks need re-applying after most windows updates - and can even fail while using the computer (usually if resources get tight).

Would be awesome to have a native fix within Reaper - as this is what is visible on my screen 99% of the time.

[fourdogslong]

Originally Posted by Gruust

Download the sources as a zip file, install Visual Studio (check Desktop C/C++ development) and CMake (choose "put on path for everyone").

Unpack the sources, open native tools command Prompt (press windows key, enter x64 and it should pop up), navigate to the sources, then enter:

cmake -B build
cd build
cmake --build . --config Release

And if you want to debug or fire up Visual Studio:

explorer ReaperThemeHackDll.sln

I'm getting these errors when trying this

NMAKE : fatal error U1077: 'if not exist ..\..\bin.X64\key.snk sn -k ..\..\bin.X64\key.snk' : return code '0x1' [C:\Use
rs\mathi\Desktop\ReaperThemeHackDll-master\build\detours.vcxproj]
  Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\bin\Host
X64\x64\nmake.exe" /NOLOGO /L                 ' : return code '0x2' [C:\Users\mathi\Desktop\ReaperThemeHackDll-master\b
uild\detours.vcxproj]
  Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\bin\Host
X64\x64\nmake.exe" /NOLOGO /                  ' : return code '0x2' [C:\Users\mathi\Desktop\ReaperThemeHackDll-master\b
uild\detours.vcxproj]
  Stop.
C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): e
rror MSB8066: Custom build for 'C:\Users\mathi\Desktop\ReaperThemeHackDll-master\build\CMakeFiles\9020850dce598d61f9655
4714486b479\detours-mkdir.rule;C:\Users\mathi\Desktop\ReaperThemeHackDll-master\build\CMakeFiles\9020850dce598d61f96554
714486b479\detours-download.rule;C:\Users\mathi\Desktop\ReaperThemeHackDll-master\build\CMakeFiles\9020850dce598d61f965
54714486b479\detours-update.rule;C:\Users\mathi\Desktop\ReaperThemeHackDll-master\build\CMakeFiles\9020850dce598d61f965
54714486b479\detours-patch.rule;C:\Users\mathi\Desktop\ReaperThemeHackDll-master\build\CMakeFiles\9020850dce598d61f9655
4714486b479\detours-configure.rule;C:\Users\mathi\Desktop\ReaperThemeHackDll-master\build\CMakeFiles\9020850dce598d61f9
6554714486b479\detours-build.rule;C:\Users\mathi\Desktop\ReaperThemeHackDll-master\build\CMakeFiles\9020850dce598d61f96
554714486b479\detours-install.rule;C:\Users\mathi\Desktop\ReaperThemeHackDll-master\build\CMakeFiles\f961141eb5c68dfc8c
0fe337063dbc3f\detours-complete.rule;C:\Users\mathi\Desktop\ReaperThemeHackDll-master\build\CMakeFiles\4b7700c7cb1ec400
d8e75b3ca74db1a3\detours.rule;C:\Users\mathi\Desktop\ReaperThemeHackDll-master\CMakeLists.txt' exited with code 2. [C:\
Users\mathi\Desktop\ReaperThemeHackDll-master\build\detours.vcxproj]

Any cue about what's wrong?

[Justin]

Originally Posted by Gruust

Haha, didn't even realize it's you. If that happens, I'll buy the next few versions, too! I know only two DAWs out there that don't annoy me in dark mode. And both are really buggy. How do you guys (?) keep your code base so reliable with all those frequent updates?

It will take some time -- your proof of concept is great, but we need to try to minimize the overhead of it (e.g. avoiding the global hooks, ideally) and do it with a lot of care. Hence, it's not simple (per my original comment)...