Thank you for letting us know, we'll look into that issue for the next beta coming soon.
Correct me if I'm wrong, but isn't something like this a candidate for a hotfix? Given the large number of bugs/problems with Beta3 (especially on W10), the software is a pretty good candidate for simply uninstalling at this point.
Beta 4 is out now, does it help with this issue at all?
@Jaga1: Beta versions have bugs, they're for testing new features. We're working on resolving the issues as fast as we can so we can ship 7.3.
I'm not new to software development, let's just leave it at that.
I was making a point that the Start menu not appearing where it should dramatically impacts the usefulness of the software as a whole. i.e. it becomes very inefficient to use at that point. When your entire package is nearly worthless due to a single feature, usually you hotfix that feature giving it priority status, even in a beta.
I've seen one of the 6+ problems I've experienced with the 7.3 beta branch fixed in a week's time. I'm going to uninstall DisplayFusion until more progress is made. I simply can't use it with Windows 10, because it doesn't work with Windows 10.
The odd part - you guys had what, 9 months+ to mess with W10's Technical Preview, then 30+ days after release? This is truly disappointing. DisplayFusion is the *only* piece of software I'm using on W10 that has major issues.
A note: if you're going to have a box with a link to the Windows 10 known issues topic, you should probably update that list to reflect the true status. Anything else is either inept, or dishonest marketing.
And no, Beta 4 doesn't fix this problem. I'm almost certain I posted this elsewhere on these (or the Steam) forums yesterday.
We've just released a new DisplayFusion beta version (http://www.displayfusion.com/Download/Beta/) and this issue should be all fixed up. Please let us know if you run into any trouble after updating.
Same story with beta 5. Two monitors showing W10 menu and primary monitor (laptop) showing Classic Shell. When using Windows own multimonitor taskbar there's no problem, Classic Shell on all monitors.
Ok, strange! There was definitely an issue in Beta 4 that we fixed up for Beta 5. Sounds like your issue may be a different one then. Could you send over a debug log?
On the Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal"
Restart DisplayFusion
Try to open the Start menu on the second moniotr and note the time so we'll know where to check in the log file
Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
The latest beta 5 is working fine with classic shell, and the normal win 10 start menu.
Only issue I have noticed is the custom start icon I'm using is smaller on the displayfusion taskbar, unlike in version 7.2 where it’s the correct size.
The only program I’m using is classic shell to change the default start button. But like I said in the latest betas the display fusion start icon comes out smaller, than on the normal taskbar.