Menu

#2256 Database opens off screen

KeePass_2.x
open
nobody
None
5
2017-05-27
2017-03-28
No

When I undock my laptop and go from two screens to a single screen the main Keepass cotinues to act as if there were still two screens. While the signon/password is nicely centered on my single screen once I successful gain access to my database the page opens off screen. My workaround is to manually edit the XML file and set the X coordinate to zero the start Keepass (2.35 on Windows 7 and 10)

Discussion

  • Dominik Reichl

    Dominik Reichl - 2017-03-28

    Moving to open feature requests.

    Thanks and best regards,
    Dominik

     
    • Darryl Baker

      Darryl Baker - 2017-03-28

      This is not a feature it is a bug on how KeePass handles screen changes. I have not had this issue with ANY other program such as NotePad++, PuTTY, Chrome, Firefox, etc...

       
      • wellread1

        wellread1 - 2017-03-28

        Bugs are serious faults that cause crashes or have a potential to result in data loss. Lack of functionality that causes inconvenience is usually treated as a feature request.

         
  • Dominik Reichl

    Dominik Reichl - 2017-03-28

    Ticket moved from /p/keepass/bugs/1619/

     
  • Dominik Reichl

    Dominik Reichl - 2017-03-28

    KeePass ensures that the main window is visible when it starts. However, it doesn't do this check all the time while it's running (and as you see the window is not moved automatically); additional code will be required, which makes this a feature request, not a bug.

    Best regards,
    Dominik

     
  • Darryl Baker

    Darryl Baker - 2017-03-29

    NO THE MAIN DATABASE PAGE OPENS OFF SCREEN.from a cold start. The only page I see is the password page.

     
  • Dominik Reichl

    Dominik Reichl - 2017-03-29

    I cannot reproduce this problem. A while ago such a problem was reported though, and it was resolved by updating the graphics card driver.

    Best regards,
    Dominik

     
  • Darryl Baker

    Darryl Baker - 2017-03-29

    That I can understand. It is likely an issue with the interactions with builtin Intel HD 4X00 graphics adapter. That looks like the commonality between the two systems I am seeing the issue with. I have tried asking Windows to find a newer driver on both systems but it says I have the latest. I will do my own research to see if there are any newer drivers available.

    The details of the two systems I am seeing the issue with; my home laptop I have a an MSI G60 with a Nvidia 860M graphics card running the latest Geforce driver as well as the onboard Intel HD 4600 adapter as part of the i7-4700HQ CPU running Windows 10 and the Intel graphics driver version 20.19.15.4531, my work computer is a Dell Lattitude E4770 with the Intel HD 4400 adapter which is part of the i7-4600U processor running the Intel graphics driver verson 9.18.10.3220 running Windows 7.

     
  • Darryl Baker

    Darryl Baker - 2017-03-29

    With some difficulty I was able to replace the Dell preferred version of the Intel HD 4400 driver with the latest version from Intel itself. You are correct that does eliminate the issue.

    Now it become more of a philosophical issue. Is the lack of compatibility with a manufacturer's preferred driver when other products are a feature or is is a minor bug. After 35 years as a Unix system administrator I emphatically say bug but a minor one but whose? Not many non-computer people can force Windows to use a driver other the OEM's preferred. That mean you should accept that while technically not a bug in your code that it is you responsibility to work around the problem for your customer's to have a successful experience. It is most certainly not a feature request.

     
  • T. Bug Reporter

    T. Bug Reporter - 2017-03-29

    You are right in that this is a bug, but it is not one that can be easily fixed or worked around within the KeePass code. If you look at the entirety of the "Feature Requests" tracker here (including the closed requests, which are hidden in the default view), you will see many items that also are not technically Feature Requests; this is just Dominik's way of categorizing the work he has to do. For his purposes, and as wellread1 already said, anything that isn't a bug with the KeePass code itself gets put into his secondary tracker, which just happens to be called "Feature Requests". The fact that he hasn't closed this ticket or deleted it entirely means that he still considers it to be worthy of a solution, so please don't take the term "Feature Request" so literally.

     

Log in to post a comment.