QWT (old man yells at a cloud)

I started playing with QWT to figure out if it could be fixed, I do not have this answer, I have another question: how could this work at all :((( It is all based on weird assumptions, strange hopes that race conditions will flip the right way and so on so on. Some things make zero sense at all, like all seamless windows are part of a “hidden desktop” which leads to weird effects when they overlap (YES WHEN YOU MOVE IT VISIBLY IT GETS “MOVED” THERE TOO, AND IT IS EXPECTED TO HAVE EVENTUALLY MATCHING Z-ORDERING JUST BECAUSE F.U. THATS WHY)

[..half way done, got “native” seamless mode working without wobbling and artifacts. takes some time before it becomes something i can ship out]

I know it won’t be comforting, but you obviously didn’t hear about Big Bang theory.
That wishful thinking is the master of all

… beside practically whole science…

That’s consistent with Windows: You just have to hope that something sometimes may work …:upside_down_face:

4 Likes

first win11 build. a bit weird but somehow works.

Is it “usable”?

Already much more than original one. Fixing all the glitches. Seamless mode is finally usable and stable, no more weird borders around pop-ups and mid-window, all that is handled on the guest side. Will post MS Office screenshot once everything lands – it does the weirdest GUI abuse that stock qwt was unable to handle properly.

2 Likes

The last time I tested it on my laptop win11-vms were barely “usable”. Nice.

Does Win key invokes menu? I am asking because somehow seamless mode with WIn11 worked for me always (meaning taskbar not visible), but Win key invokes menu each time…

hm could you tell me more? also can it run ms office?

I would, but I don’t know what. I quickly tried to create a template/dvm-template/disp or named disp qubes based on win11 in order to give you more details, but wasn’t able to start those disps, and dvm-template starts, but its display, after brief showing, vanishes to somewhere I couldn’t find it afterward (nor how to switch to it, I forgot) while it is still running, and when shutting it down, its window comes back. But in a template when I enable seamless mode, I can see detached windows of started apps (notepad for example), but the window is fully shown in a template window, while a detached window at the same time (yep, weird) is white blank. I can try to debug it further if it’s not related to Xen drivers, but some qvm-features/prefs…

If you want more info, I’d need some ideas how to debug dvm-template…

Actually I found a way. I started cmd first and from there any app (explorer in the example), but you can see cloned windows in a main template window and as detached windows.

Win key also shows detached window plus in a main window…

Actually, this is how it is supposed to be, only none of this should appear even for a brief moment!
So, when I start dvm-template, and choose any app after qube started, only seamless window of that app is shown/visible. No need to post screenshots, because it’s basically the same as with a template, but without the main window.

Named disposable works perfectly in the same manner.

Still cannot start fully disp qube based on a win-11-dvm-template.

If you want me, I can installl M$ Office and try to start its apps, but I see no reason them not to function the same way…

Rather than a full blown win spyware cluster I would like to try either a completely minified windows or Wine or something. It is only a few apps that I really need windows for.

Seamless windows are working in my named disposable too, even for M$ Office

So, I don’t know why it doesn’t work for others. It always worked for me, and this whole new setup creating Windows 11 qubes from scratch, installing QWT and M$ Office created only for the purpose of this topic are stock, vanilla, not customized anyhow and it works out of the box.

Not a single issue with performances, or any other kind.

Interesting, what is the MS Office version?

2016

hm, interesting. what is different about my system so i got all kinds of ugly bugs

wine is not really better with office newer than 2010

got rid of ugly double mouse pointer, too. and you can resize non-seamless desktop as you wish, no more fixed resolutions.

1 Like

So, my implementation is based on IDD userland driver, thus from security perspective it should not add to attack surface neither for LPE nor for dom0 breakout. It imposes certain limitations we did not see in stock QWT because the mechanism was fully absent there: resolution change from dom0 non-seamless window resize is a full-blown monitor PnP event, like disconnecting old one and plugging in anew. But it is not a big deal, I optimizied this path and it happens fast.

1 Like