Aug 16 2018 02:33 AM
Aug 16 2018 02:33 AM
Feedback-hub does not work in 2019 preview so I chose this way.
These are my comments on topic "what I do not like about Windows 2019".
I upgraded to Windows 10 and downgraded back to 8.1 many times (3 times I think) in last 3 years.
I just did not like W10 desktop visual state.
Now I tested W2019 a little and it seems that it is better but not good enough.
Windows Server 2019 standard, 17723, 180720-1452
Scale (Display\Scale and layout) changing to 100 % (default is 150 %) causes problems.
Many windows were like bitmap down-scaling instead of drawing smaller fonts.
With basic graphics driver it looks really strangely.
Everything was ok after reboot.
Search line stopped to work.
It did not find anything (incl. cmd, mspaint).
That happened only once.
I do not know why, but some characters are red shaded.
Same problem is in W81.
I wonder how you are able to add those red shades to the character.
I tested a few render methods and neither produced red characters.
A) best result (characters are more weighted and readable) and 5x faster rendering (using less CPU) than using DrawText
same visual result for all D2D1_OPACITY_MASK_CONTENT variants in my case
B) less thick, some characters are to shallow
C) bad with ANTIALIASED_QUALITY (with small characters), better with NONANTIALIASED_QUALITY
When I switch off font-smoothing I expect it to be switched off in all OS windows.
At the moment it is some kind of mix bag.
Other non-os applications have their own behavior off course, but VS is definitively strange as well.
Could you add font-smoothing checkbox to mspaint ?
I needed many times to do some corrections in 20 years old bitmaps and only solution is:
-go to system dialog and switch off font smoothing
-do bitmap correction
-go to system dialog and switch on font smoothing
Lost input response.
Computer is completely stuck when you are running 4 processes on 4 core CPU.
It is impossible to get to CTRL+ALT+DEL screen, it takes minutes to get only black color.
So I added Sleep(1000) after 60 s.
Then you are barely able to run task manager and kill those processes.
I think it should work like that:
-to give boost above runtime class to the process handling that CTRL+ALT+DEL screen
-to give boost to task manager run from that window
-very important is to set top window property - no other top window should lay over that task manager
I remember lost input states like these from W2000 days and nothing changes today as we can see.
DWORD tick0 = GetTickCount();
DWORD tick = GetTickCount();
if ((tick - tick0) > 60000)
tick0 = tick;
Window showed under parent window some times.
I was able to reproduce it only in hyper-v machine.
What happened to UI0Detect ?
I remember that interactive service detection was broken in first W10.
When the screen switched to that with service processes, no mouse and keyboard was functional and desktop screen returned back after 30s.
Now it seems it is completely gone.
Empty tooltip on dialog's item (picture 8).
There is missing Windows(CR+LF) / Unix(LF) encoding selection in notepad when creating new file.