Unsolved
This post is more than 5 years old
27 Posts
0
1430
DDM, usage issues, bugs?
Hello,
System:
Windows 10
Display Manager: 1.31.0.1899
1. In Windows 10 a window which has been maximized to the screen can be clicked with the mouse on its upper bar and then dragged in order to reduce its size. But this behavior no longer functions when screen split mode is selected inside Display Manager.
2. Lets say you have a Word window open taking up your screen. Now if you click on Display Manager icon it shows as usual but now if you click back into your active Word window, Display Manager will not close. It only closes when you click on a third window, having to switch away from the primary Word window you are working on. Also could you make the close (X) button in Display Manager bigger, because it is tiny !!
I have emailed the company supporting it, but maybe if other people are experiencing these bugs , they will have more incentive to fix them.
swamped207
3 Apprentice
3 Apprentice
•
426 Posts
0
January 18th, 2018 04:00
Your #1 is a feature of Windows Snap, which is disabled by DDM when Easy Arrange is enabled to avoid conflicts. Do a search here for "Kbfix" or "LeaveSnapAlone" for registry settings that allow Easy Arrange and Snap to coexist.
As for your #2, the dialog box automatically closes after ~30 seconds, allowing you to go back and make further changes to image levels and the preset mode for the active app without having to go back and reopen the dialog box.
(Agreed on the size of the close button.)
3ukman
27 Posts
0
January 26th, 2018 05:00
The end result is that the user must point to the tiny x to close the window. 5 sec time out or adjustable interval is more acceptable.
So user has to click this tiny x every time.
If they want to adjust the brightness of the image, hovering over the quick view should be enough to keep it open, and not having to click the tiny x to hide it. Simply making the button slightly larger is not enough to fix the user experience flaw.
swamped207
3 Apprentice
3 Apprentice
•
426 Posts
0
January 26th, 2018 10:00
I wasn't disagreeing with you, just pointing out that that behavior was by design and not a bug.
In the current rc, the small dialog box closes immediately when it loses input focus, just like the Windows clock/calendar.