Hi Jon
I am using the latest beta 101, and the "move to X resize problem" that I reported last week for the previous release is fixed - thanks! However, I see another possible glitch. I have set up a hotkey with 2 commands: (i) move window to monitor 2, followed by (ii) move to top left of monitor. I assigned it to a title bar button.

When a window is on monitor 1, and I click that title bar button, it performs perfectly. BUT if the window is ALREADY on monitor 2 (say, in the center of the screen on monitor 2) and I click the button - nothing happens. I'd expect the window to move to the top left of the monitor. However, DP seems to say "wait a minute, this window is already on #2, so I will just ignore the subsequent command in this hotkey, of "move to top left"".

Maybe this is by design, but intuitively I'd expect the window to move to the top left of the monitor....
ScotProf

Hi Jon

Just DL'd & installed beta 2; no change in this behavior ......

Hi,

I can confirm this is still an issue too. It was introduced with beta 1 if that helps.

Cheers,

Darren

Jon,

Seems to be fixed with beta 3.

Thanks,

Darren

Thanks for fixing this in B3, Jon.

Hi I'm not sure if this is related but it seems so. Allow me to elaborate.

I'm using Beta 7 and I have the Taskbar Button Middle-Click Behavior mapped to "Move to next monitor"
Even with Taskbar Middle-Click Behavior set to "Do nothing", when I middle click any icons in my Primary Monitor taskbar it ends up opening a new instance. Even after exiting the program it is still performing this behavior.

The good news is, the Move to next monitor function seems to be working perfect with the Secondary Monitor taskbar now.

Thanks, I love the program by the way.

That taskbar setting ONLY effects the DF taskbar.

No biggie, wasn't certain if the primary taskbar always behaved this way or not. Figured when I quit the program and it still did it, was probably just something always featured in Windows 7 that I never noticed.
My original post was about the DF taskbar middle-click issue that's resolved with the new beta but I edited it.