Visio 2013 VERY slow

MVP's are not granted general access to developers.  Over time some do develop personal contacts with developers when they meet them at conferences and such.

While 8 months should be enough time for a bug fix to be developed, tested and rolled out, FIRST it has to move to the top of the development list.  For that to happen it has to be a high profile bug, ie major media coverage (like hacking/data loss) or a "pet" feature "owned" by a manager with pull.

Reporting problems here is one of the accepted "bug" reporting methods. As well, here are some other places you can make feature request suggestions and bug reports:

Your satisfaction Matters! Let us know your thoughts about your Microsoft experience.

https://secure.opinionlab.com/ccc01/o.asp?id=yDnqREvN

MS has a very large audience, so if you want your suggestion to be acted upon you need many people to make the same suggestion. So ask your friends, fiends <grin>, enemies, relatives, co-workers, strangers on the street to also submit your suggestion to all of the following locations.

Here is proof  that once in a blue moon MS does actually listen to user input about some of its “stupid” design decisions: http://www.theregister.co.uk/2012/05/09/visual\_studio\_11\_grey\_no\_more/

So “.. yes Virginia …”, it is worth complaining about the stupid ribbon, or other pet peeve, they sometimes pay attention.

But then again, when I looked at the “before” and “after” I don’t see much improvement!  I’m afraid this is a fore-runner for a “metrified” Office 15.  Well, we’ll see.

Another example of MS sometimes listening is found in Outlook. In 2010 MS removed the “Unread” messages view from Outlook.  In 2013 the “Unread” view is returned.

There are examples of how well the “listen”, like the 2013 Preview White color scheme. The “fix” is 14 new application bar designs, but only 2 new shades of grey color schemes (no blue or black like previously) …

<snip Comment from a “Softie” in the Answers Forum>

Hi, I'm an engineer on the Word product team. Thanks for your feedback. JairOV is correct: unfortunately, we cannot comment on unannounced product updates and decisions. However, we take customer feedback seriously when designing future versions of our product, and frequently monitor these forums for feedback and suggestions.

</snip>

http://www.outlook-tips.net/tips/outlook-2013-50-shades-gray/ 

In addition, this page has screen captures of Outlook 2013 RTM (don’t miss reading the comments, they are hilarious): 

http://www.slipstick.com/outlook/2013/changing-office-2013s-color-scheme/  

Screen caps of new “color” scheme.  But at least they have a choice of 14 “background designs” for the title bars.  Well, there you go, we can see that they certainly have their priorities straight  <sigh>

https://skydrive.live.com/redir?resid=E9A78C332557256F!297&authkey=!AGZ-GhCx9Q1ZUug – JPG comparing color schemes from 2003-2013(RTM)

https://skydrive.live.com/redir?resid=E9A78C332557256F!298&authkey=!AN36Nw-TqH6py2M – Original DOC comparing Color Schemes from 2003-2013 (RTM) allows you to zoom in for more details

Microsoft: Tell us what you think - Feedback

http://mymfe.microsoft.com/support.microsoft.com/feedback.aspx?formid=24

http://office.microsoft.com/en-us/suggestions.aspx?sitename=CL100569831033&type=0

http://office.microsoft.com/en-us/suggestions.aspx Feedback

NOTE: when you post comments / suggestions it is best to limit each submission to one issue. That way replies can be specific to that error. And it makes it easier for MS to assign a submission to a specific development group or person.

MS Office 365

http://mymfe.microsoft.com/Microsoft%20%20Online%20%20Services/Feedback.aspx?formID=210

Office 2010

http://mymfe.microsoft.com/Office/feedback.aspx?formID=375

http://office.microsoft.com/en-us/suggestions.aspx Feedback

http://www.worldstart.com/ms-office-2010-putting-in-your-2-cents/print/ (it is something of a run around, but there are links to lots of good resources too)

Office 2007

http://mymfe.microsoft.com/Office%202007/Feedback.aspx?formID=81

Win7

http://mymfe.microsoft.com/Windows%207/Feedback.aspx?formID=195

https://feedback.office.microsoft.com/default.aspx?productkey=office2007&scrx=1

Internet Explorer

http://mymfe.microsoft.com/Windows.com/Feedback.aspx?formID=123

Isn't it enough for Microsoft to pay attention for this problem?

8 months from first time users reported about it.

MVPs read this thread, they should have developers' contacts.

Or is there way to report a bug?

I am having the same issue,  Has this been resolved?  Super annoying.  I would not even think of developing anything in 2013.  I still do all my development in 2010 and only us 2013 on my surface when I am in a remote location (FYI: pan and zoom don't work correctly regardless of mouse or touch screen use).  Funny thing is that all need to do is pan and zoom.... nothing else...

Mitch

Its always worth checking the 'auto-save' was not kicking in making the pan/zoom appear slow.

When in fact the files are being saved in the background.

@DB007

While the issues you've listed are also valid concerns.  They're not related to the pan/zoom issue originally posted in this thread.