-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FZ Editor] Displaying the monitors layout #8104
Comments
There would be two approaches to drawing these monitor previews. One would be to change the container from horizontal to vertical when we detect vertical orientations. This one should be easier to code, but it would be limited to horizontal/vertical layouts. The other would be to create some kind of a canvas and draw them there. Now I'm not exactly sure how to do this but we can give it a try. For that, it would make sense to get physical pixel coordinates for each monitor, just like Windows does in the Display settings. |
@niels9001 |
@niels9001 @SeraphimaZ Has this already been resolved? |
@dedavis6797 Nope. What is the main benefit of this? To recognize which screen is which? |
I'm not sure myself. I actually misread the description and didn't catch the full context on what was being requested here, but I understand now. This's just looking to draw the monitors in the editor at the same orientation/positions as they're set in the Windows Display settings. I guess I can seem some benefit to this, but I agree this should still be a rather low priority. I just wanted to get a better understanding on when this would land since it keeps getting punted. |
It's for recognizing which screen is which when they're aligned vertically. Some users find it disturbing when they see monitors not in the same way as it is in the system settings. |
📝 Provide a description of the new feature
PT version: 613d1fd
When using the new multi-monitor FancyZones editor #6562, the monitors should be drawn similarly to how they're drawn on the Windows 10 Display settings page. Since changing this impacts the UI perhaps it should be done after #6899 is merged.
The text was updated successfully, but these errors were encountered: