Opened 13 years ago
Closed 12 years ago
#8256 closed bug (fixed)
[Terminal] remember color schema settings [easy]
| Reported by: | Disreali | Owned by: | siarzhuk |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/Terminal | Version: | R1/Development |
| Keywords: | GSOC2012 | Cc: | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Using hrev43534, but it has been around for quite awhile.
Steps to reproduce:
- Open Terminal -> Settings -> Settings.
- notice that the Color schema dropdown box is set to 'Custom', and the Color dropdown and ColorChooser(is that the proper name?) are 'live' and can be changed.
- Select a pre-defined Color schema from the dropdown box.
- notice that the Color dropdown and the ColorChooser are now grayed out and no longer 'live'.
- Click the 'OK' button to save settings and close the Settings window.
- Repeat step 1
- Notice that the Color schema dropdown is once again set to 'Custom', and that the Color dropdown and ColorChooser are again 'live' and not grayed out.
Once a user has selected a pre-defined color schema, the settings window should remember it and show it as selected every time the settings are opened.
Attachments (1)
Change History (18)
follow-up: 2 comment:1 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 13 years ago
Replying to siarzhuk:
Are you using non-English locale?
No. The system locale is en-US. I did not know that made a difference.
comment:3 by , 13 years ago
| Summary: | [Terminal] remember color schema settings → [Terminal] remember color schema settings [easy] |
|---|
by , 13 years ago
| Attachment: | 8256_terminal_colorschema.patch added |
|---|
comment:4 by , 13 years ago
| patch: | 0 → 1 |
|---|
follow-up: 7 comment:5 by , 13 years ago
| Keywords: | GSOC2012 added |
|---|
follow-up: 9 comment:8 by , 13 years ago
Replying to siarzhuk:
GSOC2012
???
Ups. :-( All is OK. Thank for the submission, luckypower!
Sorry for the noise!
comment:9 by , 13 years ago
follow-up: 11 comment:10 by , 13 years ago
Any explanation for the patch? I haven't looked at the related code, but just looking at the patch I wonder why a == operator should not compare certain attributes. Intuitively I'd say that's the wrong place for a fix.
follow-up: 12 comment:11 by , 13 years ago
Replying to bonefish:
Any explanation for the patch? I haven't looked at the related code, but just looking at the patch I wonder why a
==operator should not compare certain attributes. Intuitively I'd say that's the wrong place for a fix.
I suspect that both cursor colors of the Color object are not used at the moment. So if the Color objects really contain not-initialized trash here - it is not a wonder why user see the "Custom" scheme every time he tries to set the pre-defined scheme. So the patch can be related to the real source of problem and can be counted as valual for GSoC. From the other side I have on my TODO list many tasks related to Terminal problems and restoring normal colors support is one of them I'm dreaming all this years when my MC goes to acid "green instead white" color scheme. ;-) Thats why I do not applied this.
follow-up: 13 comment:12 by , 13 years ago
Replying to siarzhuk:
I suspect that both cursor colors of the Color object are not used at the moment. So if the Color objects really contain not-initialized trash here
I would suspect something like that as well, but if that's the case, the better solution would be either to remove these attributes completely (not just in the == operator) or -- particularly if there's any intention to use them in the future -- initialize them properly (and keep the comparison in the == operator).
follow-up: 14 comment:13 by , 13 years ago
Replying to bonefish:
Replying to siarzhuk:
I suspect that both cursor colors of the Color object are not used at the moment. So if the Color objects really contain not-initialized trash here
I would suspect something like that as well, but if that's the case, the better solution would be either to remove these attributes completely (not just in the
==operator) or -- particularly if there's any intention to use them in the future -- initialize them properly (and keep the comparison in the==operator).
You are right. Correct initialization of the object fileds is looking like more correct way to solve theproblem at the moment. ;-)
comment:14 by , 13 years ago
Replying to siarzhuk:
Replying to bonefish:
Replying to siarzhuk:
I suspect that both cursor colors of the Color object are not used at the moment. So if the Color objects really contain not-initialized trash here
I would suspect something like that as well, but if that's the case, the better solution would be either to remove these attributes completely (not just in the
==operator) or -- particularly if there's any intention to use them in the future -- initialize them properly (and keep the comparison in the==operator).You are right. Correct initialization of the object fileds is looking like more correct way to solve theproblem at the moment. ;-)
Thanks for correcting me. cursor_fore_color and cursor_back_color was not set when we change the schema. So i thought it must not be checked when we compare schema. But I will come up with better solution, as both of you suggested.
follow-up: 16 comment:15 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
solved in hrev44955
comment:16 by , 12 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Are you using non-English locale?