Theme doesn't work correctly #637

Open
opened 2021-01-22 14:10:53 +01:00 by ghost · 6 comments
ghost commented 2021-01-22 14:10:53 +01:00 (Migrated from github.com)

It looks like this in settings:
image

It looks like this in settings: ![image](https://user-images.githubusercontent.com/68649672/105494803-a1e96780-5cbb-11eb-8288-0b33f430b08c.png)
Lateralus138 commented 2021-05-26 17:09:29 +02:00 (Migrated from github.com)

Yep, mine looks like this as well. I don't use this term often, but I like it, just not much time to look into the issue myself it or I'd fork it. Maybe later this year.

Yep, mine looks like this as well. I don't use this term often, but I like it, just not much time to look into the issue myself it or I'd fork it. Maybe later this year.
MrAureliusR commented 2022-04-16 10:43:31 +02:00 (Migrated from github.com)

Having the same issue, glad I found an existing issue to bump instead of opening a new one.

image

I'm using KDE with the default Dark Breeze theme on Arch Linux. This is the only window in any app that I've seen act like this. It definitely was readable and normal at some point in the past, because I remember tweaking the settings when I first installed it. So at some point it stopped working. I might try building older releases to see if I can pinpoint when the change happened, assuming it's on CRT's end...

I'd be happy to help debug the issue in any way, but with the huge number of open issues... well, let's hope this gets some attention eventually :) This isn't my main terminal emulator, or else I'd probably roll my sleeves up and try and track down the bug myself, but I just don't have the time right now.

Having the same issue, glad I found an existing issue to bump instead of opening a new one. ![image](https://user-images.githubusercontent.com/41264289/163668478-becd02f8-ce77-4e3a-b2d8-6440e0a4566e.png) I'm using KDE with the default Dark Breeze theme on Arch Linux. This is the only window in any app that I've seen act like this. It definitely *was* readable and normal at some point in the past, because I remember tweaking the settings when I first installed it. So at some point it stopped working. I might try building older releases to see if I can pinpoint when the change happened, assuming it's on CRT's end... I'd be happy to help debug the issue in any way, but with the huge number of open issues... well, let's hope this gets some attention eventually :) This isn't my main terminal emulator, or else I'd probably roll my sleeves up and try and track down the bug myself, but I just don't have the time right now.
MrAureliusR commented 2022-04-16 11:03:01 +02:00 (Migrated from github.com)

Okay, I've done a bit of digging. I cloned the repo, and built the latest commit, which has the issue. Then I checked out 1.1.1 which, while it does have a white border in the settings menu, is perfectly readable and normal. Then I used bisect to narrow down the commit, and it was commit dae1a56691 which caused the issue. So moving from QtQuick.Controls 1.x to 2.x or updating the QMLTermWidget submodule is what caused the issue.

Hope this helps a bit, I might try playing around to see exactly which change caused the issue.

Okay, I've done a bit of digging. I cloned the repo, and built the latest commit, which has the issue. Then I checked out 1.1.1 which, while it does have a white border in the settings menu, is perfectly readable and normal. Then I used bisect to narrow down the commit, and it was commit dae1a56691841cbc37d597c5da59bfbc91e1e1a9 which caused the issue. So moving from QtQuick.Controls 1.x to 2.x *or* updating the QMLTermWidget submodule is what caused the issue. Hope this helps a bit, I might try playing around to see exactly which change caused the issue.
Darthpenguin commented 2022-09-16 03:32:29 +02:00 (Migrated from github.com)

I thought I was having this issue becasue I'm using the Cinnamon desktop instead of KDE plasma. But I guess the problem exists in KDE also.

I thought I was having this issue becasue I'm using the Cinnamon desktop instead of KDE plasma. But I guess the problem exists in KDE also.
wd5gnr commented 2023-01-11 14:51:41 +01:00 (Migrated from github.com)

Try quick workaround: launch like this:

QT_QUICK_CONTROLS_STYLE=Material cool-retro-term

Ugly, but you can read it. This bug is in a few different places.

Try quick workaround: launch like this: QT_QUICK_CONTROLS_STYLE=Material cool-retro-term Ugly, but you can read it. This bug is in a few different places.
denilsonsa commented 2023-03-17 14:44:09 +01:00 (Migrated from github.com)

FYI, these styles serve as workarounds:

QT_QUICK_CONTROLS_STYLE=Imagine cool-retro-term
QT_QUICK_CONTROLS_STYLE=Material cool-retro-term
QT_QUICK_CONTROLS_STYLE=Universal cool-retro-term
FYI, these styles serve as workarounds: QT_QUICK_CONTROLS_STYLE=Imagine cool-retro-term QT_QUICK_CONTROLS_STYLE=Material cool-retro-term QT_QUICK_CONTROLS_STYLE=Universal cool-retro-term
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: seeseemelk/cool-retro-term#637
No description provided.