Insider build of Windows 10 shows more easy configuration of refresh rate changes

Discussion in 'Frontpage news' started by Hilbert Hagedoorn, Oct 15, 2020.

  1. Hilbert Hagedoorn

    Hilbert Hagedoorn Don Vito Corleone Staff Member

    Messages:
    39,188
    Likes Received:
    7,834
    GPU:
    AMD | NVIDIA
    southamptonfc and NightWind like this.
  2. NightWind

    NightWind Member Guru

    Messages:
    171
    Likes Received:
    136
    GPU:
    Asus ROG 2060 Super
    It was a good idea. Thanks.
     
  3. The Goose

    The Goose Ancient Guru

    Messages:
    2,526
    Likes Received:
    112
    GPU:
    MSIrtx2080 superXS
    Now all they need to do is add the bit rate, given that after a driver update i have to change the bit rate on both my screens to 10bit this will add 3.5 secs to my day opening 2 apps every time theres a driver refresh
     
    GSDragoon and southamptonfc like this.
  4. Silva

    Silva Maha Guru

    Messages:
    1,248
    Likes Received:
    457
    GPU:
    Asus RX560 4G
    I don't think its about saving 3.5 secs, it's about not hiding everything in menus. I find W10 much more difficult to configure compared to W7, the menus are atrocious.
    These options are hidden inside old menus that look like they are from WXP or something.
     
    sykozis, schmidtbag and southamptonfc like this.

  5. southamptonfc

    southamptonfc Ancient Guru

    Messages:
    1,869
    Likes Received:
    92
    GPU:
    STRIX 2080 Super
    Just think how many people would lose their jobs if designers didn't flip flop all the time.

    1. Design out a critical piece of functionality, developers implement.
    2. Support channels flooded with questions and complaints - support/CRM need to get involved.
    3. A year later, design the critical functionality back in, developers implement.

    The whole IT community should be grateful for designers!
     
    Silva likes this.
  6. Shakey_Jake33

    Shakey_Jake33 Master Guru

    Messages:
    276
    Likes Received:
    24
    GPU:
    GeForce RTX 2060 OC
    Now if only more games would let you select a refresh rate in-game.
     
  7. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    16,987
    Likes Received:
    2,526
    GPU:
    AMD S. 5700XT Pulse
    What's been changed that's where the refresh rate setting is anyway isn't it?

    EDIT: Yeah I'm not seeing a difference here unless people were going into the device manager and display hardware properties for this for some reason??
    (Or the GPU control panel which should work just fine too.)

    [​IMG]

    EDIT: Is this backported as some funny thing Microsoft just kinda flipped on for 20H2 or something?
     
    Last edited: Oct 15, 2020
  8. Alessio1989

    Alessio1989 Ancient Guru

    Messages:
    1,874
    Likes Received:
    513
    GPU:
    .
    I would like to see more responsive XML interfaces with less white on wide and ultra wide screens..
    BTW 5 years to move a drop-down value choice...
     
    JonasBeckman likes this.
  9. schmidtbag

    schmidtbag Ancient Guru

    Messages:
    5,387
    Likes Received:
    1,941
    GPU:
    HIS R9 290
    Maybe you could create a .reg or .bat file to force-adjust it and have it run at boot. Not ideal but better than going out of you way to fix it every time.

    Yeah, I'm not a fan of the new control panel, because too many things are missing. I've found myself pretty much entirely depending on the search tool to get anything done. It's also just really cumbersome, particularly if you're trying to configure multiple different things at the same time.
     
    Silva likes this.
  10. chanw4

    chanw4 Ancient Guru

    Messages:
    2,346
    Likes Received:
    21
    GPU:
    Sapphire R9 280
    so, 2 click (1. open adaptor properties windows, 2. change to corresponding tab) less compare to current build

    Yea, some of the settings in the new control panel are all over the places.
     

  11. mbk1969

    mbk1969 Ancient Guru

    Messages:
    9,849
    Likes Received:
    6,803
    GPU:
    GF RTX 2070 Super
    That`s XAML, and the responsiveness is not about XAML, but about WinRT - completely new runtime, new OS API for UWP apps.
    XAML is just a markup language to hold the UI (and used not only in UWP apps, but in legacy desktop apps written with WPF for user interface).
    But of course, XAML is based on XML.
     
  12. Aura89

    Aura89 Ancient Guru

    Messages:
    8,059
    Likes Received:
    1,213
    GPU:
    -
    You are on an insider version, so it appears that they implemented this on an earlier insider version, but are just now talking about it.
     
  13. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    16,987
    Likes Received:
    2,526
    GPU:
    AMD S. 5700XT Pulse
    Yeah 19041 / 19042 are fairly similar to how the previous build was handled (Shared updates and a enablement package that activated the new build features.) and I'm thinking a lot of focus is on the new builds for next years update of the OS now so 20H2 can't be far off from full release.

    Same stuff in the cumulative updates which are now out for all users as of the latest monthly patch rollout and update cycle but there is that enablement package which bumps the build up by one and activates these extras for 20H2 and that also does a install for Edge Chromium as part of that process.


    There's not much with this though at least that Microsoft has listed far as I can find.

    Theme aware start menu tiles.
    Alt-tab support for Edge tabs.
    Quick access to pinned sites in Edge.
    Personalized task bar for new accounts.
    Improved notifications.
    System page in the control panel is migrated to the settings app.
    Tablet experience improvements for 2-in-1 devices.
    Chromium Edge as the new default browser.
    Modern Device Management policies.

    Think that's it.
    (Not a huge fan of re-linking control panel settings to open the app instead and a page there but the rest is fairly small changes to the OS.)

    One never really knows though what else is enabled with this even if the underlying code is identical with this .572 or KB4579311 update along with the servicing stack update and updates to .NET and the final update for Adobe Flash before it's discontinued.

    Servicing stack is this.
    https://support.microsoft.com/help/4577266

    Cumulative is this one.
    https://support.microsoft.com/help/4579311

    And .NET 3.5 / 4.8 just to throw that in too cause why not. :p
    https://support.microsoft.com/kb/4578968


    Interesting if they did include this feature into the 20H2 update instead of the 21H1 builds though, also taking quite a while for the actual enablement pack here to hit public release for 20H2 too which I think started around the .450 somewhere updates and said enablement pack which has only been updated once so far just adding a newer Edge Chromium version into it.

    Can't be too long now though, 21H1 should wind down to bug fix mode too soon and then launching in April / May I assume is the idea with this cycle although it sounded like Microsoft considered changing back to a yearly rollout but that didn't happen.


    EDIT: All that said though there's several thousand changes between Windows 10 builds and numerous tweaks and adjustments and even the build announcement is a highlight of specific features so the full number of changes usually takes a while to show up compared to what Microsoft is highlighting.
     
    Last edited: Oct 16, 2020
  14. Alessio1989

    Alessio1989 Ancient Guru

    Messages:
    1,874
    Likes Received:
    513
    GPU:
    .
    WinRT is just a (almost) 0-overhead C++ wrap upon a part of Winapi (win32+COM). You can use almost every WinRT API in common desktop applications too and not having those crap GUI results. Those interfaces are crap XAML (which is just XML with some crap resulting in auto-compiled code) usage. You can write hard-coded GUI in WinRT too without having those shitting results, plus you usually don't use both WPF and XAML in the same application, unless for some reason you are migrating a WPF GUI to XAML. The fake responsive design used in almost all Microsoft UWP apps and in the "new" control panel are just terrible design choices and poor usage of their own platform tool-sets.
     
    Last edited: Oct 16, 2020
  15. Ghosty

    Ghosty Ancient Guru

    Messages:
    5,386
    Likes Received:
    100
    GPU:
    3200U
    I could change my refresh rate in Windows 98.
     

  16. Astyanax

    Astyanax Ancient Guru

    Messages:
    7,985
    Likes Received:
    2,667
    GPU:
    GTX 1080ti
    and without rebooting the system! (unlike windows 95)
     
  17. mbk1969

    mbk1969 Ancient Guru

    Messages:
    9,849
    Likes Received:
    6,803
    GPU:
    GF RTX 2070 Super
    https://en.wikipedia.org/wiki/Windows_Runtime
    https://docs.microsoft.com/en-us/windows/uwp/get-started/universal-application-platform-guide
     
  18. theoneofgod

    theoneofgod Ancient Guru

    Messages:
    4,418
    Likes Received:
    180
    GPU:
    RX 580 8GB
    You mean like this?

    [​IMG]
     
  19. mbk1969

    mbk1969 Ancient Guru

    Messages:
    9,849
    Likes Received:
    6,803
    GPU:
    GF RTX 2070 Super
    What are you talking about? XAML was introduced with WPF in 2006 and it offers such benefits that it became an "industry" standard to contain UI in XAML:
    https://en.wikipedia.org/wiki/Windows_Presentation_Foundation
    When you create new WPF project in VisualStudio the initial UI created from template is always held in XAML, and you can edit it in special designer. If you remove XAML file from the project and create UI in the code you loose the ability to use UI designer.
    Also professional designers use Microsoft Blend - very powerful editor which utilises XAML files only.
    Also another thing which became a standard too - MVVM - is not possible without XAML files.

    So I have no idea what are you talking about. Maybe school projects can avoid using XAML files but professional ones can`t.
     
  20. Alessio1989

    Alessio1989 Ancient Guru

    Messages:
    1,874
    Likes Received:
    513
    GPU:
    .
    I don't care about what you state or wiki, I care what I see in the SDK when I work with Visual Studio. WPF was born for .NET environment, so C#/VB.net (and no, it's was not native for C/C++, since you have to use that garbage of CLI language extension), another piece of garbage tool for people that don't know what the hell they are doing 'cause they are all but CS or real programmers (if you cannot deal with pointers and threads synchronization you are just a hobbyist or a hipster that wanna give itself a title that doesn't own). The so called "designers" should go back in kindergarten and do some finger-paint.

    Blend is another piece of crap for making more crap & slow interface with XAML. Now it's directly compiled into per-packed shitcode. Yes using that native C++ wrapper around Winapi with the old good COM (WRL is just another mid-level wrapper too, so I don't count it) works better than CLI and .NET, but doesn't matter.

    Oh yes, I almost forgot it...before there was another piece of garbage between C++/CLI and native WinRT called C++/Cx, another piece of garbage that could be easily outperformed by C# and .Net.

    Fortunately someone had enough of that crap and made proper port (well, it was almost a dismantling) called now "C++/WinRT" and now he works at Microsoft. And all that's was really.. dumb, since the WinRT was just per-compiled native code with meta-interface for C#/VB.NET/JS and that crap called C++/Cx, but Kerr work was also better than the closed piece of junk used inside at Microsoft itself that it become not only part of the current SDK but also the tool used ow at Microsoft, giving cleaner code and better performance.. This is also why you don't have any limitation and can made amazing interfaces with WinRT if you get rid-off of XAML.
    So yes, another failure for the managed languages team... and guess what, it was just a black-box upon COM interfaces using the good old WinAPI (one of the favorite ranting aim of some trash sites and their common viewers.. but that's another story of ignorance and the abuse of the internet from people that should go back to the abacus..).

    XAML interfaces are crap and the usage Microsoft made and continue to do into it's own UWP applications and the "new" (can be called new after 5 years even if it's not end at all?) control panel is crap too.
    XML-like based interface works for phone since you have just to do a dumb GUI. They sucks on PC since they cannot handle an enriched I/O environment of multi-resizable windows upon (multiple) screen of different sizes, form factors and capabilities, as well as the classic combo mouse+keyboard...

    So sorry, but you or any other "fake" tech site/journalist/wiki/self-satisfaction article/video made by MS will ever change my mind. I dealt with them even too much and I don't wanna go handling with them again.
     
    Last edited: Oct 17, 2020

Share This Page