Skip to content
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

unremovable background image #387

Closed
atommaki opened this issue Feb 18, 2021 · 3 comments
Closed

unremovable background image #387

atommaki opened this issue Feb 18, 2021 · 3 comments

Comments

@atommaki
Copy link

atommaki commented Feb 18, 2021

Describe the bug
There is no way (on the GUI) to remove the background image once you set it up.

To Reproduce

Go to Preferences -> Profiles -> your profile (probably "default") -> Background
choose a background image. As soon as you start a new terminator instance you see the background image, all works fine till this point. Now try to remove this background image in the Preferences. There is no way. You can choose another image, but no option to remove your chosen picture from the setup.

Expected behavior

Should be an option to remove the image from the setup (clear).

BTW: this part of the preferences anyway looks quite confusing, asking for a refactoring. You can choose between "solid color" and "transparent", but you can not choose the color because it's on another tab (colors) and there is no radio button to choose the "background image" option. As soon as you setup a background image even choosing the "solid color" option doesn't remove the background image

Workaround
Set the "shade the background image" to 1.0, it makes the image invisible.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • Ubuntu 20.04, teminator 2.1.0

Screenshot from 2021-02-19 00-16-24

@mattrose
Copy link
Member

Are you sure you're using 2.1.0? I see an entirely different preferences pane in 2.1.0. The one you see is from 2.0, IIRC. Here's mine

Screen Shot 2021-02-18 at 6 21 58 PM

@mattrose
Copy link
Member

As you can see, that one makes much more sense, and works as you want it to.

@atommaki
Copy link
Author

Sorry, my fault. Indeed I was using 2.0.1. It works fine now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants