Split-Pane with &#39;backgroundImage&#39; set, not showing all background images #8790

@DHowett commented on GitHub (Jun 3, 2020):

... which profile has the background image?

@DHowett commented on GitHub (Jun 3, 2020): ... which profile has the background image?

claunia commented

@sleepnmojo commented on GitHub (Jun 3, 2020):

I had it on my default (Windows Powershell 5.1) and Command Prompt. I get the same behavior if I do wt -p "Command Prompt" ; split-pane -p "Command Prompt".

@sleepnmojo commented on GitHub (Jun 3, 2020): I had it on my default (Windows Powershell 5.1) and Command Prompt. I get the same behavior if I do `wt -p "Command Prompt" ; split-pane -p "Command Prompt"`.

claunia commented

@sleepnmojo commented on GitHub (Jun 3, 2020):

These are the relevant sections of my settings:

    "profiles":
    {
        "defaults":
        {
            "fontFace": "FiraCode",
            "colorScheme": "Darkly",
            "cursorShape": "filledBox",
            "useAcrylic": true,
            "acrylicOpacity": 0.9,
            "padding": 3,
            "historySize": 32767
        },
        "list":
        [
            {
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name": "PowerShell 5.1",
                "commandline": "powershell.exe",
                "colorScheme": "Darkly Powershell",
                "hidden": false,
                "backgroundImage": "C:/Windows/Web/win.png",
                "backgroundImageOpacity": 0.05
            },
            {
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "icon": "ms-appx:///ProfileIcons/{0caa0dad-35be-5f56-a8ff-afceeeaa6101}.scale-100.png",
                "name": "Command Prompt",
                "commandline": "cmd.exe",
                "hidden": false,
                "backgroundImage": "C:/Windows/Web/win.png",
                "backgroundImageOpacity": 0.05
            }

I tried turning off backgroundOpacity, and removing all the defaults, the issue persisted.

@sleepnmojo commented on GitHub (Jun 3, 2020): These are the relevant sections of my settings: ``` "profiles": { "defaults": { "fontFace": "FiraCode", "colorScheme": "Darkly", "cursorShape": "filledBox", "useAcrylic": true, "acrylicOpacity": 0.9, "padding": 3, "historySize": 32767 }, "list": [ { "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "name": "PowerShell 5.1", "commandline": "powershell.exe", "colorScheme": "Darkly Powershell", "hidden": false, "backgroundImage": "C:/Windows/Web/win.png", "backgroundImageOpacity": 0.05 }, { "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "icon": "ms-appx:///ProfileIcons/{0caa0dad-35be-5f56-a8ff-afceeeaa6101}.scale-100.png", "name": "Command Prompt", "commandline": "cmd.exe", "hidden": false, "backgroundImage": "C:/Windows/Web/win.png", "backgroundImageOpacity": 0.05 } ``` I tried turning off backgroundOpacity, and removing all the defaults, the issue persisted.

claunia commented

@zadjii-msft commented on GitHub (Jun 4, 2020):

Wait is the commandline you're using wt -p "Command Prompt" ; split-pane -p "Windows PowerShell" or wt -p "Command Prompt" ; split-pane -p "PowerShell 5.1"?

@zadjii-msft commented on GitHub (Jun 4, 2020): Wait is the commandline you're using `wt -p "Command Prompt" ; split-pane -p "Windows PowerShell"` or `wt -p "Command Prompt" ; split-pane -p "PowerShell 5.1"`?

claunia commented

@sleepnmojo commented on GitHub (Jun 4, 2020):

They actually give the same result. The Command Prompt side shows no background image, the PowerShell side shows the background image.

I was using wt -p "Command Prompt" ; split-pane -p "Windows PowerShell", but I see why you ask, my profile is named PowerShell 5.1. I don't have a profile named, "Windows PowerShell", so it looks like it is loading the default profile. Regardless, wt split-pane produces the same issue.

I can also reproduce the issue with wt -p "Command Prompt"; split-pane -p "Command Prompt"

@sleepnmojo commented on GitHub (Jun 4, 2020): They actually give the same result. The Command Prompt side shows no background image, the PowerShell side shows the background image. I was using `wt -p "Command Prompt" ; split-pane -p "Windows PowerShell"`, but I see why you ask, my profile is named `PowerShell 5.1`. I don't have a profile named, "Windows PowerShell", so it looks like it is loading the default profile. Regardless, `wt split-pane` produces the same issue. I can also reproduce the issue with `wt -p "Command Prompt"; split-pane -p "Command Prompt"`

claunia commented

@epoweripione commented on GitHub (Jun 15, 2020):

This issue seems to occur randomly, i met a few times, maybe the backgroup image too large (~350KB) and load timeout?

I run Windows Terminal 1.0.1401.0 on Windows 10.0.19041.329, Using: $env:comspec /c wt new-tab -p Debian; split-pane -p "PowerShell Core" -V

My profile settings:

    "profiles": {
        "defaults": {
            "fontFace": "FiraCode Nerd Font Mono",
            "fontSize": 12,
            "acrylicOpacity": 1.0,
            "useAcrylic": true,
            "cursorShape": "underscore",
            "backgroundImage":"%USERPROFILE%\\Pictures\\wt_bg.jpg",
            "backgroundImageOpacity" : 0.3,
            "backgroundImageStretchMode": "uniformToFill",
            "backgroundImageAlignment": "center",
            "colorScheme": "One Half Dark"
        },
        "list": [
            {
                "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
                "name": "PowerShell Core",
                "commandline": "pwsh.exe -NoLogo",
                "hidden": false
                // "source": "Windows.Terminal.PowershellCore"
            },
            {
                "guid": "{58ad8b0c-3ef8-5f4d-bc6f-13e4c00f2530}",
                "name": "Debian",
                "commandline": "wsl.exe ~ -d Debian",
                "hidden": false
                // "startingDirectory": "%USERPROFILE%/wslhome"
                // "source": "Windows.Terminal.Wsl"
            },
            {
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name": "Windows PowerShell",
                "commandline": "powershell.exe",
                "hidden": false
            },
            {
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "name": "cmd",
                "commandline": "cmd.exe",
                "hidden": false
            },
            {
                "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
                "name": "Azure Cloud Shell",
                "source": "Windows.Terminal.Azure",
                "hidden": false
            }
        ]
    },

@epoweripione commented on GitHub (Jun 15, 2020): This issue seems to occur randomly, i met a few times, maybe the backgroup image too large (~350KB) and load timeout? I run `Windows Terminal 1.0.1401.0` on `Windows 10.0.19041.329`, Using: `$env:comspec /c wt new-tab -p Debian; split-pane -p "PowerShell Core" -V` My profile settings: ``` "profiles": { "defaults": { "fontFace": "FiraCode Nerd Font Mono", "fontSize": 12, "acrylicOpacity": 1.0, "useAcrylic": true, "cursorShape": "underscore", "backgroundImage":"%USERPROFILE%\\Pictures\\wt_bg.jpg", "backgroundImageOpacity" : 0.3, "backgroundImageStretchMode": "uniformToFill", "backgroundImageAlignment": "center", "colorScheme": "One Half Dark" }, "list": [ { "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "name": "PowerShell Core", "commandline": "pwsh.exe -NoLogo", "hidden": false // "source": "Windows.Terminal.PowershellCore" }, { "guid": "{58ad8b0c-3ef8-5f4d-bc6f-13e4c00f2530}", "name": "Debian", "commandline": "wsl.exe ~ -d Debian", "hidden": false // "startingDirectory": "%USERPROFILE%/wslhome" // "source": "Windows.Terminal.Wsl" }, { "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "name": "Windows PowerShell", "commandline": "powershell.exe", "hidden": false }, { "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "name": "cmd", "commandline": "cmd.exe", "hidden": false }, { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "name": "Azure Cloud Shell", "source": "Windows.Terminal.Azure", "hidden": false } ] }, ```

claunia commented

@sleepnmojo commented on GitHub (Jun 22, 2020):

The image I'm using is 125KB. Its dimensions are 7111x4000. It is a png, with transparency.

@sleepnmojo commented on GitHub (Jun 22, 2020): The image I'm using is 125KB. Its dimensions are 7111x4000. It is a png, with transparency.

claunia commented

@zadjii-msft commented on GitHub (Jun 23, 2020):

By any chance, does resizing the window a little bit cause the image to load? I'm honestly just grasping at straws at this point. Does opening more that two panes with the image work?

I've tried locally with a profile with a background gif to no avail, so maybe the image size has something to do with it, but honestly I've got no ideas.

@zadjii-msft commented on GitHub (Jun 23, 2020): By any chance, does resizing the window a little bit cause the image to load? I'm honestly just grasping at straws at this point. Does opening more that two panes with the image work? I've tried locally with a profile with a background gif to no avail, so maybe the image size has something to do with it, but honestly I've got no ideas.

claunia commented

@sleepnmojo commented on GitHub (Jun 23, 2020):

Resizing or maximizing shows the background image.
The issue only happens on two panes. If I have three or more panes, then all background images show.

I changed the background image to a 46KB jpg (1920x1080), and I still have the issue.
I changed the background image to a 496KB gif (320x180), and I did not have the issue.

@sleepnmojo commented on GitHub (Jun 23, 2020): Resizing or maximizing shows the background image. The issue only happens on two panes. If I have three or more panes, then all background images show. I changed the background image to a 46KB jpg (1920x1080), and I still have the issue. I changed the background image to a 496KB gif (320x180), and I **did not** have the issue.

claunia commented

@zadjii-msft commented on GitHub (Mar 8, 2022):

Hey we've had piles of changes to the codebase over the last 18 months since this was filed - any chance you're still seeing this? This seems like the kind of thing that might have been fixed by a refactor along the way.

@zadjii-msft commented on GitHub (Mar 8, 2022): Hey we've had piles of changes to the codebase over the last 18 months since this was filed - any chance you're still seeing this? This seems like the kind of thing that might have been fixed by a refactor along the way.

claunia commented

@sleepnmojo commented on GitHub (Mar 11, 2022):

Microsoft Windows [Version 10.0.19043.1526]
Windows Terminal Version: 1.11.3471.0

wt split-pane still does not work.
wt -p "Command Prompt" ; split-pane -p "Command Prompt" does not work either
wt -p "Command Prompt" ; split-pane -p "PowerShell 5.1" works now
wt split-pane;split-pane still works
wt split-pane;split-pane -p "Command Prompt" works

Looks like if I load two of the same instance, the issue is there. Go to three, it is gone. Two different instances, then no problem.

@sleepnmojo commented on GitHub (Mar 11, 2022): Microsoft Windows [Version 10.0.19043.1526] Windows Terminal Version: 1.11.3471.0 `wt split-pane` still does not work. `wt -p "Command Prompt" ; split-pane -p "Command Prompt"` does not work either `wt -p "Command Prompt" ; split-pane -p "PowerShell 5.1"` works now `wt split-pane;split-pane` still works `wt split-pane;split-pane -p "Command Prompt"` works Looks like if I load two of the same instance, the issue is there. Go to three, it is gone. Two different instances, then no problem.

claunia commented

@zadjii-msft commented on GitHub (Mar 11, 2022):

@sleepnmojo can you try out this preview build, v1.13? https://github.com/microsoft/terminal/releases/tag/v1.13.10395.0

I just realized that the refactor I'm thinking of might only be in 1.13

@zadjii-msft commented on GitHub (Mar 11, 2022): @sleepnmojo can you try out this preview build, v1.13? https://github.com/microsoft/terminal/releases/tag/v1.13.10395.0 I just realized that the refactor I'm thinking of might only be in 1.13

claunia commented

@ghost commented on GitHub (Mar 15, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Mar 15, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.

claunia commented

@sleepnmojo commented on GitHub (Mar 17, 2022):

Microsoft Windows [Version 10.0.19043.1526]
Windows Terminal Preview Version: 1.13.10395.0

Problem still occurs with these two commands
wt split-pane
wt -p "Command Prompt" ; split-pane -p "Command Prompt"

@sleepnmojo commented on GitHub (Mar 17, 2022): Microsoft Windows [Version 10.0.19043.1526] Windows Terminal Preview Version: 1.13.10395.0 Problem still occurs with these two commands `wt split-pane` `wt -p "Command Prompt" ; split-pane -p "Command Prompt"`

claunia commented

@zadjii-msft commented on GitHub (Mar 17, 2022):

Help, thanks for trying, sorry we didn't just magically fix this one. I can't repro this myself so I suppose we'll need someone who actually can repro this to take a look. Thanks for confirming for me!

@zadjii-msft commented on GitHub (Mar 17, 2022): Help, thanks for trying, sorry we didn't just magically fix this one. I can't repro this myself so I suppose we'll need someone who actually can repro this to take a look. Thanks for confirming for me!

claunia commented