Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-9301

Window does not get restored after minimization

XMLWordPrintable

    • Severity 2 - Major

      After minimizing Sourcetree using the minimize button in the window title bar, it is hardly possible to restore the window again. Maybe one out of ten trials is successful, i.e. the Sourcetree window is restored. In all other instance you hear only the Windows notification sound.

      This is independent of the window state (regular/maximized).

      When Sourcetree is minimized via the application icon in the task bar (single click while active), another click on the icon will restore the window without problems.

        1. image-2018-12-12-11-30-39-689.png
          image-2018-12-12-11-30-39-689.png
          5 kB

            [SRCTREEWIN-9301] Window does not get restored after minimization

            Anphy Jose (Inactive) added a comment -

            Already fixed in the latest version

            Anphy Jose (Inactive) added a comment - Already fixed in the latest version

            Anphy Jose (Inactive) added a comment -

            Hi falk.martin, for scaling there is another issue already raised - https://jira.atlassian.com/browse/SRCTREEWIN-7039

            Closing this specific one.

             

            Anphy Jose (Inactive) added a comment - Hi falk.martin , for scaling there is another issue already raised -  https://jira.atlassian.com/browse/SRCTREEWIN-7039 Closing this specific one.  

            falkmartin added a comment -

            Just tested with version 3.4.2, the problem appears to be solved. Tested successfully on multi-screen setup.
            However, now I am faced with incorrect dpi scaling First display 3000x2000 pixel, dpi scaling 150%, second display 2560x1440, dpi scaling 100%. The SourceTree UI on the second display is way too large. This was not a problem before with 3.3.x.

            falkmartin added a comment - Just tested with version 3.4.2, the problem appears to be solved. Tested successfully on multi-screen setup. However, now I am faced with incorrect dpi scaling First display 3000x2000 pixel, dpi scaling 150%, second display 2560x1440, dpi scaling 100%. The SourceTree UI on the second display is way too large. This was not a problem before with 3.3.x.

            Apoorv Singhal (Inactive) added a comment -

            Anyone facing this issue, can you please check in the latest version 3.4.2 
            https://product-downloads.atlassian.com/software/sourcetree/windows/ga/SourceTreeSetup-3.4.2.exe

            Apoorv Singhal (Inactive) added a comment - Anyone facing this issue, can you please check in the latest version 3.4.2  https://product-downloads.atlassian.com/software/sourcetree/windows/ga/SourceTreeSetup-3.4.2.exe

            Igor Kachkovsky added a comment - - edited

            I frequently reproduce this issue(sometimes after click windows "minimize all" button) on 3.0.8 with win 10.
            I changed SXGA monitor to QWHD and the issue is still reproducing.
            I also have same issues with screens "Log selected" and "annotate selected". I am sure they all have one reason.

            Igor Kachkovsky added a comment - - edited I frequently reproduce this issue(sometimes after click windows "minimize all" button) on 3.0.8 with win 10. I changed SXGA monitor to QWHD and the issue is still reproducing. I also have same issues with screens "Log selected" and "annotate selected". I am sure they all have one reason.

            syedsameerali added a comment -

            I am not running a 4k display. Although I have a multi monitor setup (2x monitors @1080p, 1x Display Link USB Monitor @1080p, 1x LG HDTV @1080p ).

            This issue is one I have been encountering since October of 2018 (ST-Win ^3.0.8). I have not tested versions prior to that so I can not say for certain which version of Source-tree first introduced the bug.

            I had first reported the issue while I was using a laptop, After which, I purchased a new desktop PC, with a new Windows installation. Unfortunately on this new system as well, I am still experiencing the same issue (ST-Win 3.0.15). 

             

            syedsameerali added a comment - I am not running a 4k display. Although I have a multi monitor setup (2x monitors @1080p, 1x Display Link USB Monitor @1080p, 1x LG HDTV @1080p ). This issue is one I have been encountering since October of 2018 (ST-Win ^3.0.8). I have not tested versions prior to that so I can not say for certain which version of Source-tree first introduced the bug. I had first reported the issue while I was using a laptop, After which, I purchased a new desktop PC, with a new Windows installation. Unfortunately on this new system as well, I am still experiencing the same issue (ST-Win 3.0.15).   

            skst added a comment - - edited

            I'm running Sourcetree 3.1.2, and the problem seems to have been resolved.

            I'm not running a 4K monitor, but it is UW-QHD (3440x1440).

            skst added a comment - - edited I'm running Sourcetree 3.1.2, and the problem seems to have been resolved. I'm not running a 4K monitor, but it is UW-QHD (3440x1440).

            minnsey added a comment -

            Hi

            Can I check, those of you still experiencing this problem are any/all of you running 4k monitors? We have found a WPF issue with 4k monitors, there is a fix for that on its way.

            minnsey added a comment - Hi Can I check, those of you still experiencing this problem are any/all of you running 4k monitors? We have found a WPF issue with 4k monitors, there is a fix for that on its way.

            Travis Nguyen added a comment -

            @Baurzhan. Me too, I cannot active source tree when I minimize it.

            Travis Nguyen added a comment - @Baurzhan. Me too, I cannot active source tree when I minimize it.

            capslocky added a comment -

            3.0.17 still has this bug. Win 10, 2 monitors. Workarounds are hitting 'Enter' either 'Win'+'Up'.

            capslocky added a comment - 3.0.17 still has this bug. Win 10, 2 monitors. Workarounds are hitting 'Enter' either 'Win'+'Up'.

              mcorsaro Mike Corsaro (Inactive)
              df476c939026 falkmartin
              Affected customers:
              73 This affects my team
              Watchers:
              55 Start watching this issue

                Created:
                Updated:
                Resolved: