Jon,

I've found that occasionally "drag a maximized window to a different monitor" doesn't work. It is consistently not working at this moment though it is enabled in Window Management. I expect (though don't know because I can't test now) that the problem will go away when I reboot. I just installed 3.1.8 on a machine that has been up for many days, but I've seen the symptom intermittently before. Anything I can do to help you troubleshoot?

Attached is the troubleshooting info from Settings and a bit of the end of the log after making attempts to drag a window. Note that I did also move the windows I failed to drag by clicking my move to monitor #X titlebar buttons.

Here's the log. It already began with the install of the product as if the upgrade actually deleted the previous log. It is long...

[color=gray]No, can't reboot right now. But like a said, issues like this usually appear after the machine has been up for a while. At the next reboot, I'll report back. If it happens again (even if after an install, e.g., the beta, etc.), do you want an update?
[/color]
Okay, at this point in writing my reply, I decided to exit DisplayFusion and run it again. The problem went away. Though I doubt it will be diagnostic, I've attached the log showing the shut down and most of the start up of the application (at 14:35.34). Interesting note: The app keeps writing to the log file every few seconds for minutes after start-up. My notepad replacement (PSPad) kept on notifying me of changes until I had to do my nosing about back in notepad. Enjoy!

Any clues to why hooking is failing?

No, I didn't reboot. Next time I update DF, I'll check the drag. I'm guessing that the install process is what is causing the hooking problem. Now that I know that I just need to stop DF and start again to get it to work properly, I'll try that. I'll report back if it makes a difference next time.

Well, when beta 4 comes out I'll check it out (that is if it doesn't require a reboot)...

It did require a reboot... Wasn't able to test the symptom. After roboot, of course, it worked fine.

Any suggestions or requests?

Jon,

Calling this one complete without confirmation is a little bit optimistic? Please send info on how to prevent needing to reboot next time you have a new version so I can test.

The reboot thing has more to do with the current state for your system. As far as the issue is concerned you said that it worked fine. the best way to prevent DF asking for a reboot is to close it before the update and do the update manually.

@Kevin - I was unableto test the symptom which occurs only if a reboot is not required, but thanks for the info: it was the reminder I needed. Next beta, I'll close DF (and all other apps to assure there isn't a shared system DLL), and then I'll upgrade. That should allow me to test properly.