-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Welcome/examples page completely black #2
Comments
hey, thanks for raising this! looks like they added a bunch of new keys in version 12. i'll let you know when the theme's updated and ready for a test run. |
In my opinion, it is Trolltech's responsibility to look at them - because missing key's implementation/assign shall not prevent GUI building. Visual Fallback principle is not applied there. BTW, Thank you very much for your beautiful theme! I can no longer code without it. I've made little changes here and here and wow! Mixed Latte IDE GUI with the macchiato (modified to my particular tastes) for the code editor. |
Any updates on this? |
@KraziMeanieDev @backwardspy @TheSunCat @oldlonecoder Forked and FixingI should have all 4 variants fixed by tomorrow since it's the weekends and I actually have the time. I already fixed Frappe by hand, and I'm writing a Python script that'll assume the color palette will come from the same variables in the It should take care of the other three variants automatically, assuming the color palette is constant in its location in the That script should be able to fix most themes broken by this new change. I'll pass it along here in the issue, separately from the PR with all 4 variants fixed, once it's done and I confirm everything works, so that you guys can use it for yourselves to fix any other themes that broke because of this new update. Here's the current state of Frappe post-fix.Note Although both the theme and editor theme have to both be applied, or else the editor theme gets messed up, and any open files should be closed and re-opened for the editor theme to show correctly (which should be its own PR at QtCreator). It's easier to just apply the UI theme, restart, then apply the editor theme, restart, to be sure it displays right, otherwise some of the nonsense from the previous style carries over: I'll take care of this, don't worry. I don't really use Qt Creator that much anymore, but Catppuccin is one of my goto's in Neovim, so I have a quite a fondness for this theme. It shall regain its rightful place in Qt Creator once more (: Oh and thank @ACCSCI for bringing this to my attention! |
Quick update: that Python script grew way out of control in terms of scope, and is gonna be something more useful than originally intended. I'll port the remaining two manually today as that'll be way faster at this point; I've been focusing too heavily on the script. It's hardly a script at this point, but its own Qt application that's turning into somewhat of a theming utility to generate themes from color palettes (which I grabbed from catppuccin.com), and is a much more intuitive way to create and edit themes than the built-in dialog in Qt Creator, as it takes care of all three files at once.. I kinda may or may not have gotten carried away.. a little.. maybe.. How fitting that it'll be Christmas when I'm done and give them a final pass of polish (would make more sense for Latte to have purple buttons than the default green Qt buttons, no?) As for the |
Hi! Thanks so much for maintaining my favorite color scheme for Qt Creator. I've been using it for a few months and recently updated Qt Creator, only to be greeted with this welcome page:
I am using both the creatortheme and the style, with the mocha variation. Qt Creator prints this on start, which is likely related:
The rest of the program appears unaffected. I am using Qt Creator 12.0.1 based on Qt 6.7.1, from nixpkgs.
The text was updated successfully, but these errors were encountered: