Just upgraded from B94 to B95.
I have a two-monitor setup and I prefer to place WL8 on the right one.
After upgrade to B95 it *always* starts on the left monitor. Positioning it on the right one and closing in the hope it "remembers" its last location doesn't work, it still starts on the left.
Hope this gets fixed soon.
I have a two-monitor setup and I prefer to place WL8 on the right one.
After upgrade to B95 it *always* starts on the left monitor. Positioning it on the right one and closing in the hope it "remembers" its last location doesn't work, it still starts on the left.
Hope this gets fixed soon.
Rename
So, we had to add some code to check if the window position was outside of the primary monitor size. Because if someone who ran it in a multiple monitor setting previously launched it in a single monitor mode, it could appear off the screen and inaccessible. It looks like this change led to a side effect for you.
Can you try moving WL8 to the desired monitor, and then saving the default workspace? When you restart with the saved default Workspace it should put WL8 on the correct monitor.
If that doesn't work we'll need to figure something else out.
Can you try moving WL8 to the desired monitor, and then saving the default workspace? When you restart with the saved default Workspace it should put WL8 on the correct monitor.
If that doesn't work we'll need to figure something else out.
Unfortunately, that didn't fix the issue. WL8 still opens on the left monitor.
OK we'll roll back that change for Build 96.
I wonder what user experience is actually worse, the app going off the screen and thus inaccessible or it still being accessible but starting on the left monitor? 🤔
Ideally we’ll solve both, just need more time. Only VK has reported the other issue and we have a workaround for him.
@Glitch - I tried what you stated in Post #1. I have five displays. (Using MS terminology here.) It worked on 3 of 5 displays. The desktop is extended to all displays. The displays are arranged as follows:
![](/api/discussion/download/image/8066-Screenshot-2024-07-27-151040-png)
It worked on displays 2, 4, and 5. Display 4 is the main display. Display 5 is rotated (portrait). In all test cases, I would move WL8 to a display and maximize it. I made sure the Wealth-Lab 8 Home Page fit inside its bounding window. I was careful each time to save the default workspace and restart WL8.
Working from left to right in the screenshot above, the displays have the following resolutions:
Display 2: 3840 x 2160 - worked
Display 4: 3840 x 2160 (this is the primary display) - worked
Display 1: 1920 x 1080 - did not work - reverted to display 4
Display 3: 1920 x 1200 - did not work - reverted to display 4
Display 5: 1200 x 1920 (it is rotated) - worked
So, the problem displays were 1 and 3. I tried moving display 1 so that its top edge met the top of the main display (4). I also made sure the Wealth-Lab 8 Home Page fit inside of the enclosing window. Still didn't work.
Hope that helps.
It worked on displays 2, 4, and 5. Display 4 is the main display. Display 5 is rotated (portrait). In all test cases, I would move WL8 to a display and maximize it. I made sure the Wealth-Lab 8 Home Page fit inside its bounding window. I was careful each time to save the default workspace and restart WL8.
Working from left to right in the screenshot above, the displays have the following resolutions:
Display 2: 3840 x 2160 - worked
Display 4: 3840 x 2160 (this is the primary display) - worked
Display 1: 1920 x 1080 - did not work - reverted to display 4
Display 3: 1920 x 1200 - did not work - reverted to display 4
Display 5: 1200 x 1920 (it is rotated) - worked
So, the problem displays were 1 and 3. I tried moving display 1 so that its top edge met the top of the main display (4). I also made sure the Wealth-Lab 8 Home Page fit inside of the enclosing window. Still didn't work.
Hope that helps.
As a hardware guy, I just have to ask: Is the video driver for displays 1 and 3 (which aren't working as expected) written by the same company? Can you ask them to patch it? Exactly what feature (i.e. API call) in the video driver is broken?
It's clearly not an OS problem (otherwise none of the monitors would be working), so that kind of leaves the video driver as the culprit.
What I would do is swap the function of the video cards around so WL is using the video card with the functioning video driver so everything is working as expected. There's no point in reporting the problem to the video card manufacture unless you know which video driver API call is buggy.
It's clearly not an OS problem (otherwise none of the monitors would be working), so that kind of leaves the video driver as the culprit.
What I would do is swap the function of the video cards around so WL is using the video card with the functioning video driver so everything is working as expected. There's no point in reporting the problem to the video card manufacture unless you know which video driver API call is buggy.
No, it doesn't leave the video driver as the culprit. WL8 could have a logic issue related to window placement for multiple displays.
QUOTE:
WL8 could have a logic issue related to window placement ...
If that's true, then I would fix WL8.
I'm gathering the video drivers for monitors 1 and 3 are not written by the same video card manufacture then. You might try switching the video card functionality around to see if that makes any difference.
Displays 2, 3, 4, and 5 are attached to one AMD Radeon RX 6600. Display 1 is attached to an NVIDIA GeForce GT 730. All drivers are up-to-date. Imagine the number of broken or misbehaving applications if there are problems with video drivers misreporting placement and size information.
My vote is the problem is likely in WL8. Apparently, according to posts above, logic changes were made for build 95, and then user(s) started to report the problem.
My vote is the problem is likely in WL8. Apparently, according to posts above, logic changes were made for build 95, and then user(s) started to report the problem.
Back to normal in B96... thanks.
Your Response
Post
Edit Post
Login is required