Support and General Use > Theming and Appearance Customization

New WYSIWYG Theme Editor and other utilities in one app!

<< < (3/3)

I don't understand what you're trying to do. The Theme Editor compiles fine as native Windows application. You don't need anything WSL, and no Linux permissions involved.

The only "problem" right now is that there's a Makefile involved, so you need to use MinGW to build, you can't use VS right now (should be easy to fix, but nobody did that so far; you can use it as editor of course, and the Qt extension for VS also doesn't need anything but a Qt installation). Qt comes with MinGW support (and even the environment), so all you need is to install Qt for MinGW, Qt's MinGW tools, and (optionally, if you want an IDE) Qt Creator. Then either use the MinGW shell (Qt installs a shortcut) to run qmake and mingw32-make or open the pro file in Qt Creator. Build. Done.

Don't install random things with NuGet or apt. You don't need that. Qt brings everything that is needed. There are no linker headaches when doing it properly ...

Inclement Death:
I‘m setting up my dev environment to add features and fix bugs, not just build the latest. My VS install has a cross-compiler with CMake support and the Qt5 extension adds QMake support. Just working on getting the cross-compiler set up properly.

I want to add support for drag drop, image resizing, font conversion, and packaging themes for multiple screen sizes. Basically, I want to make it an easy to use, all-in-one theme editor. I have experience with cross-platform C++ written in Visual Studio for IoT devices running different flavors of Linux.

I don’t code professionally anymore due to a connective tissue disorder that took away most of the fine motor control in my hands and causes my joints to dislocate. I went from typing ~120 words per minute to ~30, on a good day. I’m mostly bedridden, bored as hell, and trying to help out as best I can with the tools I have.

If you're working on Windows why are you trying to cross compile? If you want to work on the code there's no benefit in not working natively since there is no need to do otherwise. It only complicates things, and if you're writing portable code there's no problem in building for another OS later. I also don't see how you want to effectively debug a GUI application remotely. Sure it's possible but why go through all those extra hoops for what? Are you running those c# frontends you mentioned on a different (cross) platform for development as well?

And btw, the Theme Editor is not a pure qmake project. Having qmake support in VS will not be enough, at least for native builds (and I don't see why that should be different for remote builds)

And setting up a dev environment usually starts with getting the current code to compile 🤔


--- Quote from: bluebrother on September 03, 2020, 01:19:06 PM ---
--- Quote from: Inclement Death on September 02, 2020, 04:48:22 PM ---Where is the bug list for the Theme Editor? Only found one bug from 2010 and no feature requests in the tracker.

--- End quote ---
While at it I also created an updated Windows binary. You can find it here:

--- End quote ---

After getting back into building a theme I looked for the theme editor again.
Sadly your google drive link does not work any more.
Do you still have the binary, and if so would you re-upload it?

Many thanks

At some point Google changed those links., seems old links broke. It's still up, try here:


[0] Message Index

[*] Previous page

Go to full version