Issue with the interface
-
I haven't figured out a trigger for this, but I've been trying. Occasionally I will go back to VS and the UI will be in this state.
Video link below... (LOUD music warning: I'm sorry in advance for the music, I forgot my headphones were toggled in OBS):
https://1drv.ms/v/s!AuWHX0h5bAoRifY14BXgOVp8BGU-Pg?e=T61kp9Restoring using View>Workspaces>"Default Workspace" gets us back in business, so it's not like the defect from before where I had to clean out the WS folder. But perhaps that was a result of me closing the program after the issue occurs? (I'll try again later...)
This has happened twice so far and these UI issues always occur when I go back into VS after a break while it was running in the background. I lock my PC at night so my monitors will shut off and leave it running overnight, so maybe something awful occurs when my displays wake back up. Perhaps if I stop leaving it up when my displays go idle it will stop occurring?...
-
I can confirm when VS is closed with a "corrupt" interface without reloading the Default, it apparently saves itself as the new default. I followed @Pat's solution and had a WS saved in case which I used to get back the original state. Video: https://1drv.ms/v/s!AuWHX0h5bAoRifY4lt8pfV_Rsi3QjQ?e=WFdylB
Once again, this issue appeared again when I left the PC on idle (monitors off).
-
@debraspicher said in Issue with the interface:
this issue appeared again when I left the PC on idle
Can you save a workspace when VS is in this broken state, and send me the workspace file? I would like to replicate this.
Also: the detached context panel is not really a bug (it can be detached by dragging).
But the document tap showing at the bottom is a bug.
-
Over and over again... This time, VS didn't like me testing the Shape builder tool on a previously edited object. VS got "tangled" and I ended up with the same minimal interface. I downloaded a saved WS and had to redo it after closing and reopening the software. Again, the problem is to reproduce this issue. I hadn't thought of saving my last WS, better to do it.
-
@VectorStyler Still happening in 1.2.049
-
@B-Vs-V Somehow I will need to replicate this. Did this look similar to earlier screenshots?
-
@VectorStyler Yes, it does: no toolbox (nothing to the left of workspace), no context panel & much less panels.
-
A consistent trigger on my machine is when my monitors go to sleep and I wake my computer out of idle. I have 3 displays hooked up at the moment and the HDMI monitor waking up later always moves my Screen 1 applications to Screen 2 (HDMI is Screen 3) and it ALWAYS messes up VS.
Right now when it does this, it does a thing where it has the min/maximize buttons only showing a grey background and nothing else. That is all that is visible and it's just in the corner by itself with everything else running on that screen completely visible. If I try to move the VS window in-between monitors using Windows Key + Shift + left/right arrow when it is in this state, it completely ignores Windows Key snapping commands.
I did manage to get it to come back by using Snapping by right-clicking on the VS instance and selecting Snap Left/Right, but it only worked once. It was usable, but in a janky state with some interface elements were overized and weird gaps appearing in places there weren't before... such as above the docked document window... but at least the interface was in the right order... I had to close and reopen it to get it back to normal.
Edit: Oh hey, it's back... I went to adjust resolution on Screen 2 and VS moved itself from Screen 2 to 3 (that's a Windows 10 quirk, not VS)... but yeah this is what it looks like if you can get it to appear... :
-
@debraspicher I will try to replicate this.
-
@VectorStyler I added a screenshot to the report. I got VS to restore itself.
-
@debraspicher said in Issue with the interface:
Screen 1 applications to Screen 2 (HDMI is Screen 3)
Are all screens at 150% scale, or do you have different scaling per screen?
-
Screen 1 is 150%; Screen 2 & 3 are 100% (2 is set wrong and needs changing, but yeah).
