...in the same way you support multiple monitors -- i.e. unique configurations per virtual desktop.

Surface Pro 4, Win10, I alternate between dual monitors and tablet-only daily, resulting in erratic realignment and dramatic rescaling of desktop modules and docks.

Or, some other solution that addresses the issues. Perhaps smart realignment and rescaling when change in dpi detected.

Using Xteme. Love it love it.

Thanks!

Hmmm... aren't you really talking about two independent issues here? Virtual Desktops and on-the-fly changes in hardware configurations?

Yes, sorry I was sitting in a waiting room when I composed that message, so I'll rephrase:

Problem: Winstep Xtreme docks and modules don't behave well when changing screen resolutions, in this case changing from dual screen a lower res 1080p monitor as the primary monitor to the significantly higher res single screen (tablet only).

Possible solutions: a) support virtual desktops as independent instances, or, b) just make the docks and modules a bit more clever in how they set there locations on dpi changes.

Thanks Jorge. You have an amazing product.

Ok, can you please describe in detail what happens now and what you think should happen? That would help.

And thanks for the thumbs up!

Had a thought, a simple solution. Allow backups to be saved with unique names and then reloaded by name. I'd make a dual monitor config and a tablet only version and load whichever is needed.

While you mull that, could you provide the path to the backup file, if that's how you do it?

Thx again.

Just saw your msg. I'll post a step by step with screenshots. Manana.

Hmmm, that is actually not a bad idea at all.

Currently backups save everything, including the actual contents of docks and the Shelf (which is no good for what you want), but I could implement some kind of 'profile' feature where only the settings are saved.

Eventually I could even come up with some way to automatically load a profile upon a specific hardware/monitor setup change.



Eh? It is wherever you last saved the backup to. The default is

C:\Users\Public\Documents\WinStep\Backups\



Sleep well - I will be looking forward to that step by step.

Update, Jorge...

I've been playing with settings (including Win 10 system settings) and have found how to make docks and desktop modules behave consistently while using a Surface Pro 4 and an external monitor (therefore, two monitors).

I had set my external monitor as my primary monitor in Win 10 display settings, and had setup the Winstep objects on that external (primary-defined) monitor. My earlier described problems had to do with whenever the external monitor was disconnected (tablet view only)... the docks and desktop modules would wind up scattered in strange locations on the Surface Pro display.

My solution is to make the Surface Pro display the primary display and place all the Winstep objects on that screen. Having done that, all elements are behaving exactly as expected, regardless of whether the external monitor is connected. This makes sense, of course. It's the default setup.

In the end it means I'm not placing any Winstep elements (except wallpaper, of course) on the external monitor. Really not a problem for me to do that.

Thanks for your support and outstanding product.

Thanks for the update, and glad you managed to work it out.

One thing though, since you've mentioned using a Surface Pro: I've had a handful of users complain that Nexus becomes 'frozen' for a few minutes when their laptop returns from sleep or hibernation.

The thing they all seem to have in common is a Surface Pro laptop. Have you ever experienced anything like that on your Surface Pro?

I've experienced Winstep screen objects freezing temporarily w/ the hour glass showing for unclear reasons. I've found that it will resolve itself (unfreeze) after maybe 30 seconds with no further ill effect -- perhaps a time-out being reached, not sure, but the freeze-timeout is of consistent duration. Can't say specifically if it is a Nexus issue. Will keep an eye on it for a more detailed understanding.

Nah, what you are describing has usually to do with accessing objects/menus/items on the network.

This is different, WorkShelf/Nexus freezes for several minutes, not seconds.