I didn't know what to call this but wanted to suggest some documentation clarification be added in the DisplayFusion user interface.

Situation: I want all misaligned monitor edges to be hard stops that can not be crossed so that I don't accidentally jump between monitors. This feels more natural to me, mainly because it is very spatially logical very predictable. In the attached layout, the left-most display is a built-in laptop screen, while the others are elevated external mounted monitors at my desk.

Right now, the settings outlined in DisplayFusion would suggest it has control over edge snagging, blocking, warping, etc., but in Win11, Windows has a setting that overrides the DisplayFusion setting. This causes confusion and frustration.

Similar to this thread: https://www.displayfusion.com/Discussions/View/sticky-edges-for-particular-monitor-edge-split/?ID=4c69f0e0-98c0-4378-819e-e2e6842bd384

If you have misaligned monitors, and don't want the mouse cursor to defy conventional physics and one-way warp between monitors when you cross a monitor edge, you need to disable the helpful super annoying setting in Windows settings. Even though DisplayFusion isn't doing it, and based on those settings you'd think it shouldn't be happening, Win11 does it for you by default.

Maybe DisplayFusion could do any of the following:
1) Automatically adjust the Windows settings to match the DisplayFusion settings with
System > Display > Multiple Displays > Ease cursor movement between displays

2) Tell user some settings are overridden by windows 11

3) Tell them, but also link/jump to edit them if possible?

Point is, this is quite a big functional feature, and I completely understand DisplayFusion doesn't doesn't ultimately control how Windows decides to change things over time, but at least alerting the user to someplace else that might override the settings shown could help save time and frustration

Originally, I was going to post this as a bug, but figured out the issue just before posting. I thought it was still worth sharing for others who might have this same issue.