I see that I can completely dim the screen on mac, but how do I do it on Windows 10?
Related
I have 3 monitors and I have set Windows to turn off my screen when the computer is idle after 5 minutes because. After the computer wakes up all of my windows lose their positions and I need to move again each window to the position I want in each monitor, this is a tedious activity.
Is there any way or configuration to avoid this behavior in Windows?
I'm using Windows 10.
I've just upgraded Xming from about 7.5 to 7.7.0.56 and colors no longer display properly in multiwindow mode.
On my Windows PC I run Xming in multiwindow mode like this:
"C:\Program Files\Xming\Xming.exe" -multiwindow
Then through a putty session to my Linux PC I start a GUI app:
gedit spawnd.start
The application appears in its own window on my Windows PC, but the colours and text looks corrupted. In Eclipse the text if not even readable.
If I start Xming with no args so it uses the default 'one window' mode it displays the GUI app correctly, but then Xming has a background that covers the whole Windows desktop.
I thought this might be a color depth issue but checking the log suggests it is using 16-bit color in both modes. From the multiwindow test:
winSetEngine - Multi Window or Rootless => ShadowGDI
winScreenInit - Using Windows display depth of 16 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 2560 height: 1440 depth: 16
winFinishScreenInitFB - Masks: 0000f800 000007e0 0000001f
winInitVisualsShadowGDI - Masks 0000f800 000007e0 0000001f BPRGB 6 d 16 bpp 16
From the 'one window' test:
winScreenInit - Using Windows display depth of 16 bits per pixel
Is there some combination of Xming settings that will let me use multiwindow mode with the correct colors?
I have an application which is PROCESS_PER_MONITOR_DPI_AWARE from Windows 8.1 and DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2 from Windows 10 v1703. My windows have the WS_OVERLAPPEDWINDOW style when in windowed mode, and I switch them to a monitor-sized WS_POPUP when fullscreening.
When I change DPI on the same monitor, a windowed-mode window get a correctly-scaled window size in the WM_DPICHANGED message on both Windows 8.1 and Windows 10 v1703. When fullscreened however, Windows 8.1 doesn't resize a fullscreen window (it keeps the same dimensions) but Windows 10 v1703 does. This means that a 2560x1440 fullscreen window at 96 dpi stays 2560x1440 on Windows 8.1 when going to, say, 144 dpi, but gets resized to 3840x2160 on Windows 10 v1703.
Is this normal i.e. is keeping a fullscreen window the same size something I should now be manually doing when receiving the WM_GETDPISCALEDSIZE message, which just used to be done automatically on Windows 8.1?
EDIT: After further testing, the WM_GETDPISCALEDSIZE message doesn't even seem to be sent if the window is fullscreen, only if it's windowed (WS_POPUP works but only if the size isn't the same as the monitor). Therefore I can't even override this behaviour, and Windows 8.1 works different to Windows 10 v1703 for fullscreened windows.
Try this:
void ShowFullScreen(HWND hwnd)
{
LONG exStyle = ::GetWindowLong(hwnd, GWL_EXSTYLE);
LONG style = ::GetWindowLong(hwnd, GWL_STYLE);
::SetWindowLong(hwnd, GWL_STYLE,
(style & ~WS_OVERLAPPEDWINDOW) | WS_POPUPWINDOW);
::SetWindowLong(hwnd, GWL_EXSTYLE, exStyle | WS_EX_TOPMOST);
::ShowWindow(hwnd, SW_SHOWMAXIMIZED);
}
Will it help to solve the problem on W8.1?
I am running octave 4.0.2 on windows 7 64 bit vm hosted on a mac with El Capitan in Parallels Desktop.
I have a Thunderbolt display with the resolution 2560x1440.
When I make the main Octave GUI window bigger than a certain size, the command window starts to flash and it displays all sorts of garbage characters. I attached a screenshot I took while the command window was flashing. It seems that a threshold for the command window is approximately 1320x965 including scrollbars, i.e. when the command window becomes bigger, it starts flashing garbage characters. The window is sensitive to increasing either the width or height. Also, if the width is smaller, it will start flashing a higher height.
Any ideas on how to fix this and what might cause it?
Thank you
Update: I posted this: http://savannah.gnu.org/bugs/index.php?47893
This issue is a bug in the software: http://savannah.gnu.org/bugs/?45220.
I would like to apply a light greenish or reddish hue to the entire desktop or select application windows using Windows 7 Aero.
Assuming this is this possible with Aero, is it possible with it so I could potentially port my application to XP?
You'd have a create a window that sits on top of the other windows you wish to dim/hue. This window would use the Aero API calls to enable transparency.
For XP, you'd have to copy the contents of the screen to a bitmap, process the bitmap to make it look like you want, and create a window over the top of the other windows showing that bitmap. This technique would also work under Windows 7, but would not allow changes to any underlying windows to show through.