Just noticed a small issue with the beta that was also present in Beta 15: when you click on a clock on the taskbar of a non-primary monitor, the mouse jumps to to clock on the primary monitor despite the calendar appearing on the monitor you summoned it on.

Edit: I also have a friend on 3.4.1 who has a similar issue. When he clicks on another clock, the calendar briefly flashes up on his primary monitor.

Edit: I've noticed that the calendar flashing happens for me as well. So my friend just does not have his mouse moving.

same here

mouse jumps to Windows taskbar.

I attach troubleshooting logs. I currently have 2 machines x86 and x64 - both exhibit the problem.
I will attach the x64 logs in the morning.

I reverted to 3.1.4, and it happened, though not consistently. When clicking on a clock, one of the following would happen:

1) The mouse would jump to the primary monitor, and the calendar would appear on the monitor I clicked on (the original issue)
2) The mouse would jump to the primary monitor, but the calendar doesn't appear. Clicking again at the cursor's new position spawns the calendar, but on the monitor I originally clicked on.
3) The calendar appears on the original monitor and the cursor doesn't jump. This only happened once or twice (I tried several times).

I have three monitors, 2 x 1920x1080 and 1 x 1280x1024. I tried it several times (in both the beta and stable release), but the 3rd option only ever rarely happened on the 1280x1024 monitor. I also only got it to happen in 3.1.4. I can't say whether this is just coincidence or it doesn't work correctly at all in the new version or just one monitor.

I've attached the troubleshooting log from Beta 17.

Keith,
I attach the log.
What I noticed today:
1) Click once on clock, mouse jumps to windows taskbar clock.
2) Move mouse back over DF clock, click again - works as it should this time.
Pete

I enabled logging, immediately reproduced it and disabled logging, so the entire log should be relevant.

Just tried out what PG said made it work, and it does work for me so long as I don't dismiss the clock by clicking somewhere else, so:

1) Click on DF clock
(Mouse jumps to primary)
(Calendar spawns on secondary display)
2) Move mouse to Second display without dismissing calendar
3) Click on DF clock
(Calendar dismisses)
(Calendar spawns again; mouse not moved)

I've attached a log of this as well.

No, the problem is still there.

same here, however I have found something that may help you narrow down what is going on.
I have Windows taskbar set to auto-hide and DF taskbar fixed.
If I fix WTB the problem goes away. Re-setting WTB to auto-hide brings it back.
Pete

I've also noticed that the cursor always jumps to the same position each time. It's one pixel from the bottom (so not the absolute bottom; one pixel higher) and the in the middle of the clock on the x axis.

se my edited message from a few minutes ago

All my taskbars are set to autohide.

... and I can also confirm that setting the Windows taskbar to not autohide prevents the issue. Setting the DF taskbars to autohide has no effect.

That works fine, thanks. Do we get deerstalkers for our detective work?

fixed here too.