Okay. So I’m now on Insider Fast Ring…

And Sets suck. Really bad. I wouldn’t expect something that’s been in development for what? At least a year to be so pitiful. Window alignment errors, incorrect fit when maximized.

This is really bad. I’m shocked at how amateurish it is after being worked on for so long.

Comments (7)

7 responses to “Sets”

  1. lvthunder

    How do you know how long they have worked on this? Do you get their timesheets?

    • jimchamplin

      In reply to lvthunder:

      Snippy snippy snippy.

      We have to take it at face value that they working on it as they continue to put "Sets improvements" in the changelogs. In the end, it doesn't matter. The current state of the feature is terrible.

      And that's still pretty surprising after they've been claiming "Sets improvements" in the changelog for quite a while now.

    • Paul Thurrott

      In reply to lvthunder:

      His time frame----at least a year---is, if anything, generous to Microsoft.

  2. rc

    I have not used it so I have no clue how bad it is.

    I just want to point out (in their defense) that the development cycle can be a strange thing, and sometimes what you'd expect to take a long time actually can get fixed very quickly toward the end. Software that seems completely broken might just be mostly superficially incomplete. Also, the things that tend to be prioritized earlier in development are the more difficult ones that might seem less important.

    Just speculating, again I haven't actually used sets yet and I have no idea what they're up to over there.

    • jimchamplin

      In reply to rc:

      That's fair. My issue is that they've been claiming "Sets improvements" for multiple builds now.

      I don't have any experience with previous releases, so I don't know if what exists now is better or worse than what came before, but, wow...

      Okay so if you open File Explorer, the top border of the window is behind the Sets titlebar. Often times if I maximize a Sets window, I can see the one-pixel window border around the left and bottom margins and can often still see a pixel of wallpaper along those same borders.

      If you restore, then re-maximize, those issues are gone, but... seriously? Why aren't they right to start with? Microsoft has gotten window management right since um... Windows 1.0. Why is this not right?

      It's honestly troubling. No wonder Sets weren't in 1803. This feature is a mess.

  3. tobyburnett41

    I like the basic premise very much, and am trying to actually use it. I don't see alignment errors, the window behaves OK for me.

    My application is to develop and test code on a remote machine, for which I use WinSCP and VS code. Both work very well, and I especially like the option of multiple WinSCP sessions in different tabs. Notes go into a tab for OneNote. Since I use multiple machines, desktops at home and work, laptop on the road, I want to be able to easily pass the environment from one to another, a promise that I haven't understood how to use yet. On a screen with sufficient vertical space, I like the tab preview that Edge has, and have asked MS to provide the same for Sets.

    So, this is so much nicer than managing multiple separate, but related windows!

    My only frustration is that I can't get Sets on all my machines. The fix to enable it no longer seems to work.

    • jimchamplin

      In reply to tobyburnett41:

      See, yeah... I installed the 17692 in a VM on another machine and everything is fine.

      I wonder now if it has to do with DPI. The portable I’m having trouble with runs at 150%, but it’s 100% on the VM.

      The feedback I filed did mention I’m at 150% DPI.