The preview feature is fine for topics, but should be disabled by default for maps. It adds no value to the Content pane and frequently makes the desktop dog terribly. 

When working with a large map, such as one containing a few thousand topics, there is no such thing as a processor fast enough to render the map at a speed that isn't irritating if the only reason for rendering it is so that you can move on and do something useful. 

The main issue with the preview screen is that while it might *occasionally* be useful, it is *always* rendered, indiscriminately.

I don't mind waiting for search results to resolve because I just ran a search which is an indication that I want the search results.

I hate waiting for the preview to resolve every time I click on a map in the Content Tab because I almost never clicked on it in order to render the preview. The time I spend waiting to be allowed to do something is a complete and unnecessary waste of my time. And it happens dozens of times per day. Hundreds of times per month. Likely thousands of times per year.

There are a number of aspects of Tridion Docs that seem to indicate a level of contempt for the time of the user, but this one is the top of the hill. It's legitimately infuriating. 

Unfortunately, we have recently received similar reports that our users are also using Task Manager to kill Pub Manager in order to proceed with their work. However, it was our understanding that the preview feature in Pub Manager renders the view locally. Doesn't that indicate an issue with the users laptop/PC or network?

I support this idea.

The Previewer is used to some (limited) degree by our writers, but it's irritating to have it loading automatically for when you select the bookmap node in the Content pane or other nodes with a lot of content that can never be loaded in reasonable time, if at all. It would be better if the user could select whether to have the preview ON or OFF.

Not only is the Publication Manager previewer slow. If I turn on the previewer under "Browse repository" and start working - for example changing metadata on several objects - everything will freeze. To fix this issue I must "kill" Oxygen in Task Manager and start from scratch. Most of my colleagues have this problem. We do have a serious issue with our network speed, but nobody seems to be able to work out where the problem is, neither my own IT people nor your product support - at least so far. This is in fact very annoying.