z1ni / disp Goto Github PK

There's already ChangeDisplayPosition. Maybe blocked by #1.

Load configurations from file (/files?) and display them (or favorites?) on the tray menu.
Blocked by #1

E.g. https://dl.dropboxusercontent.com/s/uf12ecrlzufed1e/dpi.png
First display (2560x1440) is scaled to 150%, second (1920x1200) and third (1080x1920) are not scaled.

In reality the squares in the first display do not align visually with the second display, even though they align in the screenshot.

The profile/saved config/preset could change when a process is seen and changed back to what it was after the process exits.
This might be unnecessary if/when #5 is implemented (batch files could automate this).

JSON is more common and using it eases the understanding of the config files and possibly makes it easier for other programs to read them.

This eliminates the use of config files.
This could be the default, users could also export/load the config to/from a file.

Can this be done in WndProc with the message loop?

Add empty flag to monitor struct?
What to show when friendly name is not available? GDI name? (\.\DISPLAY1 etc.)

Save to a configuration file:
MONITOR struct contents (contains DEVMODE)?

File format:

• TOML
• INI
• JSON
• Custom?

E.g. "disp -d 1 -p 1" to change display 1 to portrait mode etc.

Should we allow only one instance of disp so that other instances would contact the master process to instruct it? How is this possible? Can the message loop be used?
Seems like SendMessage can be used, but we have to have the handle of the main window stored somewhere (registry?).
https://docs.microsoft.com/en-us/windows/desktop/api/winuser/nf-winuser-sendmessage
Also Data Copy https://docs.microsoft.com/en-us/windows/desktop/dataxchg/data-copy
And also named pipes https://docs.microsoft.com/en-us/windows/desktop/ipc/named-pipes

Like the Windows display settings.

Colors make it easier to identify matching rows on different displays.