Comments
10 comments
-
I suspect this is due to the scaling/dpi of your laptop screen as the popup will be controlled by that, even if SSMS is running on the other monitor. We've no current plans to add high dpi support to SoC at this time I'm afraid. -
I understand but that's not terribly helpful to your customers with hi dpi laptops.
-
We subscribed to a Source Control license but found the tool was unusable due to our team having high dpi laptops and monitors. For example the Filter Rules page is completely ruined for us, as we cannot commit the right schemas to our main branch. Support for higher dpi monitors is always on the horizon with new display technology, might as well take care of the issue while your customers are experiencing pain.
-
For anyone else experiencing the issue, changing the resolution of monitors and relaunching the program yields a working application:
Every other application I run on this machine is now affected by this requirement. But at least I can use Source Control now. -
WinForms has supported High DPI since 2017 with .NET Framework 4.7. See High DPI support - Windows Forms .NET Framework | Microsoft Docs. All you have to do is compile against the newer version of .NET and you get high DPI support automatically.Russell D said:We've no current plans to add high dpi support to SoC at this time I'm afraid.
-
WinForms has supported High DPI since 2017 with .NET Framework 4.7. See High DPI support - Windows Forms .NET Framework | Microsoft Docs. All you have to do is compile against the newer version of .NET and you get high DPI support automatically.Russell D said:We've no current plans to add high dpi support to SoC at this time I'm afraid.
-
We've fixed this in our own WinForms based software. It's not a huge hurdle to overcome. The link Mike_C provided should help. I need to be able to use this and 2 years is a long time to wait paying for something we can't use.
-
This is a hilariously poor response from Redgate - it's 2021, not 2001. Unsurprisingly high-dpi screens are the norm now and I almost feel sorry for the Redgate developers who are presumably forced to work in their cubicles with 640x480 VGA monitors.
C'mon folks, High DPI support is widely available and would at least make a half-usable application a tad more usable. -
The next version of SQL Source Control is being rebuilt from the ground up to support multiple databases and OSs. We're building this with high DPI in mind. A preview version for SQL Server is currently available. If you'd like to give it a try, you can download Flyway Desktop at https://download.red-gate.com/checkforupdates/FlywayDesktop. For help getting started, see https://documentation.red-gate.com/fd/flyway-desktop-using-sql-server-138346958.html.
You should create a new project and then set up the connection to your development database. We're still working on the transition of existing SQL Source Control projects.
Looking forward to hearing your feedback. If you'd like, you can schedule a 30 minute chat with me at https://calendly.com/stephanie-herr/30min-1?month=2021-12. -
Thank you for this update Stephanie. Can you please reply to my question at the end of this thread? Flyway Desktop Preview available! — Redgate forums (red-gate.com)StephanieHerr said:Looking forward to hearing your feedback. If you'd like, you can schedule a 30 minute chat with me at https://calendly.com/stephanie-herr/30min-1?month=2021-12.
Add comment
Please sign in to leave a comment.
Laptop is running Windows 10 1809. Laptop screen is 4K with scaling at 250% This is being displayed on the 1980x1200 screen. This is the same issue I reported to the SQL Prompt team last year that I saw on the options menu related to how code should be formatted. I'm sure that team could help with the issue as that is now fixed in SQL Prompt and has been for a while.