Ok, will definitely add it to the to-do list.

If you don't mind me asking, what do you usually do in the Designer? We're redesigning the navigation as we move to a web-based designer. One direction we're looking at is separating some of the troubleshooting and management of workflows from the design part. And your case sounds like a use case for that.

Well, first of all I am not sure I want to use a web-based designer.  To me this is one of those features that is better suited for a windows application.  Most of my time is spent updating existing workflows.  We do create new workflows but once it is created we may be working on them for several days before they are completed, and then we will fix any issues and make changes the users requests after it is released.  That means for every workflow we create we might open the Designer a dozen or more times to modify it.  I actually like the layout of the existing Designer.  I'm also not sure I want to separate the troubleshooting from the designer.  I run the workflow dozens of times during development and I like that I can just switch between tabs to develop and run workflows.

A couple things I would suggest:

1. Add a refresh button on the running workflow.  Pressing F5 to refresh is not very intuitive.  I had to ask the question on this site to discover this.
2. When you save a workflow to disk and then publish and then save a second time it prompts to overwrite an existing file.  It does not display the prompt if you save multiple times without publishing.  The designer should recognize we are overwriting the current file and not display the prompt. 
3. We need a way to  the connection profile once for the entire workflow.  We always make changes to the workflows in our development environment which means pointing the connection profile to the test environment.  Then we will export and import these workflows into production once ready.  Now we have to go through many of the activities and change the connection profile to the production environment.  This is very prone to mistakes because we can easily miss one or more activities.  Sometimes it takes months for us to discover this mistake.  Every activity in the workflow should point to one connection profile defined in the entire workflow.
4. Provide an easier way to deploy a workflow from one environment to another.  Maybe have the ability to open multiple workflow servers at the same time (like you can do in the Administration Console) and give the ability to copy from ne workflow server to another.

Thanks for listening.