I installed and ran Steam inside Weston, when I enter Steam classic layout (not big screen), the mouse position is off where Steam thinks it's pointing at.
For example:
Here my cursor is not pointing at LIBRARY tab on the upper taskbar, however LIBRARY tab is highlighted, so Steam thinks my mouse is on LIBRARY:
enter image description here
And in settings window, it's the same, I am not pointing at the "Change" button but it is highlighted:
enter image description here
However, this problem only exists in upper taskbar, lower taskbar, and independently opened window like settings, in the middle part of Steam layout, including game list on the left, and details page of the game, cursor offset does not appear. In this picture, it shows the game name is highlighted correctly when my cursor is on it.
enter image description here
And if I open it in Big Screen mode, the problem does not appear:
enter image description here
Sorry for taking pictures from display directly because it's in a docker container and I can't correctly screenshot for many reasons. But I guarantee it's not the docker container's problem because if I ran weston&steam in a docker or directly in my local host, the same problem happened. So it should be the problem of whether weston or steam.
The cursor position is correct in the shell of and other apps running in the weston, so I think it's some wrong matching between Steam and weston, the problem is that I can't find why and where things go wrong.
I tried:
Inside Steam:
Running Steam without using weston, both in docker and out docker, it works fine.
Changing resolution (video dimensions) of Steam layout, turning off and on "Enlarge text and icons based on monitor size", "Enable smooth scrolling in web views", "Enable GPU accelerated rending in web views", "Enable hardware video decoding, if supported" in the Interface tab of settings. But it does not work.
Changing the display size for library user interface elements, it does not work.
Reading log:
Read kernel log, found no problem.
Read weston log, found some errors but running on local host also has same errors.
Read command line log, found no specific errors regarding steam layout.
Steam might not find or output cursor offset to log.
For weston:
I checked the log while starting to run weston, the resolution setting is the same as my desktop screen setting and steam setting, all are 1920x1080p. So should not be the problem of weston resolution.
I tried to add a weston.ini file to change the resolution, but failed due to seatd crash and then I felt no need for that because resolution is checked to be matched.
Inside .steam directory:
Checked same files between local host Steam folder and Steam folder in docker, either they are 100% the same, or the difference is just about timestamp. There are few files existing in docker but not on local host, I removed them and ran Steam, problem persists.
I also tried to locate the exact file where Steam layout is coded, but I didn't manage to find it.
Related
I have a weird effect in ZOOM which only appears for TCL/TK windows.
Ubuntu 18.04, GNOME window manager. ZOOM version 5.10.3 (2778) (relatively new, I was forced to do an update, the problem is also new). TCL/TK 8.6.
I start a ZOOM session and share a "portion of screen" (Share - Advanced).
I run wish from the command line. I move the wish window into the shared screen portion.
For the client users of the ZOOM session, the wish window is visible if it has the focus.
When I move the focus to another window, e.g. a terminal, outside the shared screen portion, the clients only see a black region somewhat larger than the wish window (instead of the wish window).
When I move the focus to a window, e.g. a terminal, which is at least partly inside the shared screen portion, the wish window stays visible.
If I share the entire screen in ZOOM (which is not what I want for my purposes, though), the wish window stays visible.
This is so weird, I don't even have the slightest idea what is going on. What is special about TCL/TK windows that they go black in ZOOM, but only under these circumstances?
I download the Stack Windows Manager from Microsoft store. Someone introduced it to me and said it is a great program.
Oddly, after installing it and setting it up, I cannot find out how to start using it? There is no instruction to show me how to at least organize my desktop into this "layout tool". Is there a video anywhere?
At the first launch on each screen it shows you a few layouts to select from.
After you made the selection, either use Win+Arrow keys to move windows around, or drag windows between areas with middle mouse button (usually it is also the scroll button).
There is a vb6 built desktop application EXE running in Windows environment. Sometimes, when the prompt window loads it is all scrambled. When I minimize the window and then re-open, it is fixed. Any idea what could be the root cause?
Is this a code issue? Memory issue? Graphic Card?
This I suspect is to do with the property of the command window on that particular machine.
Open cmd.exe, click on the icon, go to the property, go to the layout tab and check if it has got enough buffer size. Try to match with the machine on with its working.
I am programming a Delphi (XE3) application where mouse position is important, but I would like to be able with another mouse to be able to set breakpoints without moving the primary mouse position. I may be pressing shift or control in the application I am trying to debug, so alt-tabbing to the IDE and setting a breakpoint with the keyboard keyboard won't work. Can Windows 7 easily be set up to do this?
It's possible to attach multiple keyboards and mice to a computer, and various video games can take advantage of the multiple input devices, but the OS in general does not take advantage of that. No matter how many keyboards and mice you attach, there's still just one input queue and one cursor on the screen.
If all you need is to set breakpoints without moving the mouse, then you can navigate the input caret to the desired line with the keyboard and then press F5 to toggle breakpoints.
If you need to be able to debug without interfering with the program at all, then you might need to use remote debugging. Although the documentation suggests using Remote Desktop to operate the remote program while you're sitting at the local system, that's not what you want to do in this situation because you'll still have just one set of input devices. Instead, log on to the remote computer from elsewhere (either directly, or via Remote Desktop on a third computer). It'll help to have two computers you can access from the same chair.
I've got something happening with a little app that I made that I don't understand what the problem is. The app is just a little texted panel clock that sits above the taskbar on the second monitor. Settings are saved via inifile in the proper appdata folder, and the specs are saved properly, i.e. X and Y location, font, font style, etc.
I wanted it to run automatically when Windows boots up, so yesterday I just dragged a shortcut to the Start | Programs | Startup folder. This morning when booting up, for a moment, it loaded in the proper location, then quickly moved itself back to 0 by 0 on the X-Y plane. I looked at the inifile, and sure enough... it's Top=1133 Left=1920, just like it is supposed to be, yet windows starts it at Top=0 Left=0.
What the heck?...
Check that you have the 'position=poDesigned' as well. If you dont, it will use that setting preferentially. If this is ok, put a fixed offset in your X&Y properties to see if that is where it is defaulting to. Ideally you should be setting your desired XY position no earlier than AfterCreation, do it in FormCreate if you can because by that time the form is all yours to play with.
Brian.