Processing Ajax...

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Confirm
Close Dialog

User Image
Jeffen Nilsson
112 discussion posts
I've had this problem off and on for a few weeks and it's really strange since it seems to happen to random windows using the same actions.

The trigger to the specific window having the problem this time is this



they are all move to window X and then maximize however at the moment when posting this, foobar2000 is the only window exhibiting this behavior

I have tried deleting the trigger and remaking it.

i disabled the setting and did the restore actions to make sure no other trigger was messing with it, nothing.

i attached a video of the problem since it would be kind of wonky to try and explain it in text but basically the windows maximize on the window they are on and then move to the designated monitor and flickers a couple of times to then maximize on the selected monitor
• Attachment [protected]: 2017-01-26 19.17.18.mp4 [31,778,863 bytes]
Jan 26, 2017 (modified Jan 26, 2017)  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
If you put in a 1000ms Wait action before the move, and another one before the maximize in the Trigger rule, does that make any difference at all?
Jan 26, 2017  • #2
User Image
Jeffen Nilsson
112 discussion posts
Quote:
If you put in a 1000ms Wait action before the move, and another one before the maximize in the Trigger rule, does that make any difference at all?


The only difference it makes is the delay inbetween the actions happening.

I tried removing the "maximize window" action and ONLY run the "move window to selected monitor #1.2" and i still had the same problem so it doesnt look like it has anything to do with the maximize option in this case
Jan 27, 2017  • #3
User Image
Jeffen Nilsson
112 discussion posts
i wasn't able to reproduce this other problem when posting the topic but now i can

I also get this problem using scripted windowhandles movetomonitormaximized

Sometimes the window flickers for a second or two, but sometimes the window flickers between monitor 1.1 and 3 for over 5 seconds just maximizing back and forth.

For this example the bug only happens when the window is MINIMIZED when the script starts, doesn't matter if the window is minimized in the restored form or the maximized form
• Attachment [protected]: 2017-01-27 13.19.50.mp4 [35,399,149 bytes]
Jan 27, 2017 (modified Jan 27, 2017)  • #4
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Could you send over a debug log for this issue?
  • On the Troubleshooting tab, change the Logging drop-down to "L2: Log Detailed"
  • Reproduce the Triggers issue, and then the Scripted Function issue
  • Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
  • Disable debug logging after sending the log

Thanks!
Jan 31, 2017  • #5
User Image
Jeffen Nilsson
112 discussion posts
Quote:
Could you send over a debug log for this issue?
  • On the Troubleshooting tab, change the Logging drop-down to "L2: Log Detailed"
  • Reproduce the Triggers issue, and then the Scripted Function issue
  • Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
  • Disable debug logging after sending the log

Thanks!


here you go
• Attachment [protected]: DebugInfo.html [166,899 bytes]
• Attachment [protected]: DisplayFusion.log [1,095,581 bytes]
Feb 1, 2017  • #6
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks! The issue in the video, does that only happen when using the Window Restored Trigger rule? Or does it also happen if you manually run the Scripted Function via hotkey?
Feb 1, 2017  • #7
User Image
Jeffen Nilsson
112 discussion posts
Quote:
Thanks! The issue in the video, does that only happen when using the Window Restored Trigger rule? Or does it also happen if you manually run the Scripted Function via hotkey?


No, it only happens when i restore the window by click the minimized window in the taskbar.

Activating the trigger while the window is in windowed mode works as expected.
Feb 1, 2017 (modified Feb 1, 2017)  • #8
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ok, it looks like foobar is triggering the window restored message multiple times when restoring from minimized. I'll do some more testing here and see if I can find a way around this.
Feb 3, 2017  • #9
User Image
Jeffen Nilsson
112 discussion posts
Quote:
Ok, it looks like foobar is triggering the window restored message multiple times when restoring from minimized. I'll do some more testing here and see if I can find a way around this.


Did you get anywhere with the scripted windowhandles movetomonitormaximized?
Feb 3, 2017  • #10
Keith Lammers (BFS)'s profile on WallpaperFusion.com
I didn't no, I couldn't reproduce it here. Does it only happen with certain apps?
Feb 9, 2017  • #11
User Image
Jeffen Nilsson
112 discussion posts
Quote:
I didn't no, I couldn't reproduce it here. Does it only happen with certain apps?


yes, it only happens for the folding at home BETA control window https://foldingforum.org/viewtopic.php?f=104&t=29541
Feb 9, 2017 (modified Feb 9, 2017)  • #12
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ok, thanks! I've done some testing with that window as well and still couldn't reproduce the issue. I'll have another go at it next week and see what I can find out.
Feb 10, 2017  • #13
User Image
Jeffen Nilsson
112 discussion posts
Quote:
Ok, thanks! I've done some testing with that window as well and still couldn't reproduce the issue. I'll have another go at it next week and see what I can find out.


i did some more testing on the movetomonitormaximized problem with F@H beta.
It turns out that if i have a Trigger on restore for that same window to move it to monitor 1.1 and maximize i get the problem. However if i disable that trigger and run the movetomonitormaximized function it works like normal

So it would seem to be a conflict with this specific window which makes it run both the movetomonitormaximized AND the move to monitor #1.1 and maximize
Feb 14, 2017  • #14
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ah, that would do it, yeah. There wouldn't be any way for the Trigger to know that the window was restored because of a scripting call :(
Feb 15, 2017  • #15
User Image
Jeffen Nilsson
112 discussion posts
Quote:
Ah, that would do it, yeah. There wouldn't be any way for the Trigger to know that the window was restored because of a scripting call :(


How come that is the only window with this problem though? i have the same trigger and script for many other windows all of which work just fine
Feb 15, 2017  • #16
Keith Lammers (BFS)'s profile on WallpaperFusion.com
You're right, that doesn't seem to be an issue for other apps. The weird part is that I can't reproduce it with the F@H client either. I setup my monitors the exact same as yours, including the splits, I installed the F@H beta client, and used the same script and trigger functions as you. I'm stumped!

In the Settings > Advanced Settings window, if you enable the "Window: Use Alternate Method To Move Windows (for testing ONLY)" does that help at all?
Feb 17, 2017  • #17
User Image
Jeffen Nilsson
112 discussion posts
Quote:
You're right, that doesn't seem to be an issue for other apps. The weird part is that I can't reproduce it with the F@H client either. I setup my monitors the exact same as yours, including the splits, I installed the F@H beta client, and used the same script and trigger functions as you. I'm stumped!

In the Settings > Advanced Settings window, if you enable the "Window: Use Alternate Method To Move Windows (for testing ONLY)" does that help at all?


Yes, switching that option seems to have fixed both the problems.

i'm assuming it's not recommended to have that option on all the time so any idea where to go from here?
Feb 18, 2017  • #18
Keith Lammers (BFS)'s profile on WallpaperFusion.com
If you don't run into any issues with functions/triggers/etc when that setting is on, it's safe to leave it on. The two window moving methods each have their on weird compatibility issues on some systems, so whichever one seems to work the best, just use that :)
Feb 22, 2017  • #19
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)