BUG: Windows keep changing size and position abruptly
Using latest version 13.1.2.35, latest Windows 10 1909.
I have two monitors and have always kept a maximized window for browsing and tools on one monitor, and a maximized Viewer (F10) window to see the currently selected image(s).
It seems that a bug crept into the latest build, where either the browser or viewer window suddenly turns into a non-maximized window at some arbitrarily shifted position, in response to clicking the mouse on something (e.g. changing a parameter). When I try to fix the affected window, e.g. maximize it, the other window plays bad, and so on. Often, the only resort is to restart C1 (especially when a window is shifted upwards so I can no longer see or click its top).
Luckily I'm bald, otherwise I'd already have teared all my hair... This is so annoying.
FYI, The browser window is displayed on a 1200x1600 monitor (pivoted to a portrait orientation), and, to its left, the viewer window is displayed on a 1920x1200 monitor.
-
Hi,
I have also occasionally observed similar behavior in a dual display configuration. Usually, I fix this by reloading my custom workspace. But this is irritating, I admit.
0 -
I have a similar issue, dual display, same 1920x1200 in portrait mode.
On the one monitor I have the viewer full screen.
On the second monitor, the main window is non-maximised (I just use it as a browser), and various tools I use often are displayed on the rest of the second monitor. But these tools shift randomly, albeit slightly. It's as if the system can't quite remember where they should be. I've tried creating a new workspace, but it doesn't help.
It's not hair pulling for me, and I still have some hair left, but it certainly is irritating. When a new version arrives, it's the first thing I check.
Maybe I should submit a support case, but from what I read here I may not get an adequate response. THAT would be hair pulling, so I leave it.
0 -
Samoreen,
Reloading my workspace doesn't help. Sometimes it resets one of the windows, and even then their misbehavior continues on further mouse clicks.
0 -
I have just found one consistent reproducible instance of the bug:
Every time I click with the Loupe tool (P) on any image thumbnail in the Browser window and - voila! - The Viewer window jumps a few dozen pixels to the left.
Similarly, When I click the Focus tool (F) inside the Viewer window, the Browser window jumps to the left!
0 -
What's even more annoying is when you have more than 2 monitors. I use 4 monitors with the center being the main edit window, tool panels to the left and right, and the full size preview above. Each time that C1 is opened, all panels on the surrounding screens creep inward towards the center by a few pixels. Oddest part is that reloading the workspace doesn't change anything, even though nothing has been (re)saved to the workspace since the initial layout.
Filed multiple bug reports before, but I guess it's time to do it again...
0 -
I have this problem.
I have two 27"monitors (plus one 24 for web pages)
I have the browser in one and the viewer in another.
When I click one of them the other shifts over about inch. Then I click the other one to fix it and the other monitor shifts over an inch.One of my windows is always shifted over an inch. Then when I do certain actions one of the windows will shift over more.
It is incredibly irritating.
I put in a support ticket and received a typical response: we know about it. we can't tell you when it will (ever) be fixed.
I finally had it this morning with 13.1.3 and went back to 13.1.2 but it's still there. Using Windows.
Without wasting time chasing previous versions... Can anyone tell me the version where this started so I can revert to a version without this bug?
Did they fix it in v14?
Note: I think many of us are angry about v14. They want us to pay for an upgrade when they haven't fixed major bugs in the previous version. What's worse is they expect us to move to a subscription based service when again... they don't fix major bugs in the software. I'm paying for a yearly subscription when they ignore major bugs like this.
0 -
Yes, they fixed it in v14 (aka "21") since beta 2.
Yes, I did pay the ransom and upgraded, because I couldn't stand the bug no more. I feel robbed and violated.
0 -
I found a version of 13.1.1 on a system backup drive.
The bug is not there.
They seem to have removed all access to previous versions other than the latest which is 13.1.2 and this bug is in that version as well. Thank god I found it on this system backup.
I'm NOT paying to update to v14 to fix a bug. I bought v13 on Feb 25, 2020 and they stop supporting it ~8 months later... this is bull*hit. What a disgusting business model.
Looks like I'm on 13.1.1 until I get the urge to spend $170 USD for the new haze filter.
0
Post is closed for comments.
Comments
8 comments