Problems opening documents

Everything related to our flagship word processor.
Post Reply
crumvoc
Posts: 1
Joined: 2015-03-20 07:35:00

Problems opening documents

Post by crumvoc »

Just recently, within the last few days, my 2011 MacBook Pro has developed problems opening documents within Nisus Writer Pro. The "Finder" window that pops up is extremely sluggish, slow to scroll. Also, the "open" window is often a blank page with no "cancel" or "open" buttons at the bottom. Sometimes when a document opens, it looks like a lot of ASCII notations along with the text.

Documents are saved in a dropbox folder of just under 5 GB.

The machine is a 2011 MacBook Pro, 500 GB SSD drive, 8 MB RAM.

. Any ideas or solutions much appreciated. Thank you
User avatar
martin
Official Nisus Person
Posts: 5230
Joined: 2002-07-11 17:14:10
Location: San Diego, CA
Contact:

Re: Problems opening documents

Post by martin »

There might be a few unrelated issues at work here. Let's go over your troubles:
crumvoc wrote:Just recently, within the last few days, my 2011 MacBook Pro has developed problems opening documents within Nisus Writer Pro. The "Finder" window that pops up is extremely sluggish, slow to scroll. Also, the "open" window is often a blank page with no "cancel" or "open" buttons at the bottom.
This sounds like it could be a system (OSX) problem. The "Finder" window of which you speak is the standard OSX file opening dialog. Its functionality and appearance are largely controlled by the system, with little interaction from Nisus Writer.

The next time the problem occurs, could you please use the menu Help > Send Feedback? Be sure to enable diagnostics and checkmark the option to send along your "console log". We can take a look in the log for any signs of unusual activity.
Sometimes when a document opens, it looks like a lot of ASCII notations along with the text.
This might be related to the option "Ignore Rich Text Commands" which is available in the file opening dialog. If this checkmark is turned on for most file formats (eg: RTF, DOC, etc) the file will open displaying a large amount of gibberish codes. Can you please check if that might explain the behavior?
Post Reply