sandmann
65 discussion posts
Starting a few updates ago my non-trigger window positions returned to their default behavior. For example, I have a trigger for Opera to position the window at X,Y. If I then open a chat session inside Opera it opens its' own window, which I have manually resized to be smaller and off to the side of the main Opera window. This works fine through Opera restarts, system restarts, until I update DisplayFusion. After the DF update the chat window defaults to the full size Opera window.
Another example: In Firefox I right-click an image to save it and an Explorer window opens that I have manually resized to be smaller and off to the side of the main Firefox window. Again, this works fine until I update DisplayFusion after which the Explorer window defaults to the full size Firefox window.
I have a trigger that positions the Explorer window when I open it manually with a command that continues to work properly. So it seems the Explorer Save process and the direct Explorer program are not the same?
I don't know which v10 beta this started happening but I would appreciate it if you could fix/restore DF so other window position settings are not lost after updating.
If the settings aren't changing, I can't even imagine what in the update process would be causing something like that. Are you able to reproduce the issue if you just restart DisplayFusion?
If not, what if you install Beta 20, then update to Beta 21 again, can you reproduce it every time?
sandmann
65 discussion posts
Yes, this is easily repeatable. System restarts, DF restarts, all have no effect. It is only the DF update that causes this.
Windows itself generally remembers where windows were last opened and the window size. It is these settings that the DF update wipes out.
Individual programs sometimes force a default and in those cases I use triggers to position a window; these are not affected.
I'm running three 4K monitors on Win10 22H2. The 0,0 position is the top-left of the center monitor (portrait) so the left monitor is minus number positions (left and right both landscape) (if any of this matters).
sandmann
65 discussion posts
I actually went back to v9.1 and confirmed that it happened there too.
I only (reluctantly) updated to Windows 10 in January of last year (2022). I still prefer Windows 7 but too many programs were not working or not supported anymore so I was forced to do a clean install of Windows 10.
So what I am seeing may be a function of the Windows version and not DisplayFusion per se. In other words, Windows remembered window positions across DF updates on Windows 7, but does not on Windows 10.
Does that help clear things up?
Sort of, yeah. It wouldn't have anything to do with DisplayFusion specifically, but maybe Windows 10 is resetting the saved positions any time any application is installed or something like that.
