Custom Resolution Utility (CRU)
|
10-30-2016, 06:55 PM
Post: #2371
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(10-30-2016 10:18 AM)SweetLow Wrote: >The first number seems to be port-basedThat is not a solution. That affects all monitors with the same vendor/product ID. What if there are two of the same monitor? CRU would list two monitors, but changing one would affect the other. How will I know this will happen ahead of time? How would I reflect this in the UI? CRU is monitor-based while this method is GPU-based, so how do I mix the two without adding confusion? (10-30-2016 10:18 AM)SweetLow Wrote: >What if there are two of the same monitor? Which belongs to which?So you want to give the user an option to set a number that they won't know what to set? You're ignoring the usability aspect of this. People already have enough trouble following instructions. How would I add this to the UI without making it more confusing? I'm not trying to fight this. I'm just trying to think of a good way to implement this without confusing people, and I need a way to test it. (10-30-2016 10:18 AM)SweetLow Wrote: >How will this conflict when the new drivers support EDID overrides?How will I know which systems to use the new method and which systems to use the old method? If I offer the user a choice, where do I offer this choice? |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 81 Guest(s)