-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Rolling background image like Windows Themes #3900
Comments
This isn't something we're likely to implement in version 1.0, but we would be willing to accept community contributions here. When we eventually have an extension model, this might make a good extension. Thanks! |
Adding request for slowly panning big images; and option to configure a folder of images. |
Lumping these feature requests into this issue too, since we need a consolidated story for how to handle multiple background images. From #14111 (comment):
From #7279 (comment):
I'm also upgrading this issue to be the main issue for handling multiple background images. Seems like the desired scenarios so far are...
|
Any update on this? |
Nope. We need to come up with a reasonable spec for settings to cover the scenarios outlines above, and then someone needs to actually write the code. If someone wants to help contribute a plan here, we'd be more than willing to help review 😄 (Otherwise, make sure to go hit that 👍 and subscribe, to bump this up the priorities) |
Description of the new feature/enhancement
What about a set of rolling background images instead of a single one that Windows Terminal currently supports? Looking at the same background all the time gets boring.
I like Windows Themes w/ the desktop backgrounds slideshow feature. I download a theme and I get a set of rolling background images on my desktop. What about that same concept w/ Windows Terminal? Thoughts? 💭
Screenshot reference of Windows 10:
Proposed technical implementation details (optional)
add a
"backgroundImages" : [ "file1.jpg", "file2.jpg" ]
property toprofiles
.The text was updated successfully, but these errors were encountered: