Rehosted Workflow Designer stops changing resizing mouse cursor - by Petr Altman

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 534173 Comments
Status Closed Workarounds
Type Bug Repros 9
Opened 2/17/2010 2:47:27 AM
Access Restriction Public


After starting rehosted workflow designer mouse cursor on any splitters in WPF application does not change to resize cursor.

In VS 2010 Beta2 it works normally.
Sign in to post a comment.
Posted by DavidFromCanada on 7/23/2010 at 6:35 AM
This bug has not been fixed. The problem still exists in the RTM version. It seems that somehow, the workflow designer is setting Mouse.OverrideCursor = Cursors.Arrow, but is never setting it back to null. I have not found a suitable workaround for this problem.
Posted by Bob Riddle on 5/12/2010 at 11:07 AM
Ditto for me with the WF4 Designer. We also saw the behavior posted by rcooney below (fixes itself when expand the Arguments editor and then stays "fixed" even if you close the Arguments editor) and noticed that this does NOT "fix" itself if you instead expand either "Variables" or "Imports".

With our intended users having larger workflow designs and generally small monitors, screen space for the middle of the designer is at a premium. We really need a fix for this.
Posted by rcooney on 3/31/2010 at 6:31 PM
I'm having the same problem in a rehosted designer. I've noticed that it corrects itself when you expand the "Arguments" editor. Very weird.

Posted by Petr Altman on 3/18/2010 at 3:34 AM

When using rehosted workflow designer mouse cursor stops changing in whole application (not only in designer) which is very annoying. It would be nice to have a fix or at least a workaround.

Posted by Microsoft on 2/23/2010 at 1:57 PM
Thank you for using .NET Framework 4.0 providing feedback on the WCF and WF products. This bug is currently going to the feature team who will directly investigate the issue you are reporting. We are very eager to receive this feedback and will take care to address your input. Feel free to provide comments on the Connect site if you have concerns on the resolution of this bug.

Posted by Microsoft on 2/17/2010 at 7:01 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(