For the past day or so I have been having a problem when inserting an image, specifically a .jpg. And it's not just any jpg; it's one that was exported from Adobe Acrobat Pro.
A little background. I have created a calendar and want to insert it into my Nisus document. The calendar program (CalendarMaker 5) can export the file as a TIFF or PDF. Unfortunately, the TIFF image isn't so great. So I decided to export the calendar as a PDF and then use Acrobat to export as a JPG so that I can insert it into my document.
At first I thought the problem was, believe it or not, the location of the <Page Break> command see below. Notice you only see the "lightening bolt" (⌁) and not the lightening bolt and paragraph mark ( ¶ ). Once I deleted the ¶ on the left I could then see the entire Page Break command ( ⌁¶ ) and insert the JPG.
However, whenever I tried to insert the second page of the calendar, usually by issuing a <Page Break> command, Nisus would hang and I would get the spinning beach ball. After waiting a minute or so, hovering over the Nisus dock icon would report that the application is no longer responded and I would have to do a force quit. I have used the Send Feedback option to send in a report. I have attached, based upon a suggestion from another thread about hangs, a Sample Process report from the Activity Monitor.
As an aside, and because of the weird nature of this hang, what is the best way to create a blank page in your document so that you can add either an image or more text? What I have been doing is using the <Page Break> command but maybe this is why I'm having troubles.
Hang (or spinning beach ball) when insert .jpg
- JLSchweitzer
- Posts: 28
- Joined: 2011-10-07 08:16:23
Hang (or spinning beach ball) when insert .jpg
- Attachments
-
Sample of Nisus Writer Pro.txt- (32.05 KiB) Downloaded 328 times
- martin
- Official Nisus Person
- Posts: 5230
- Joined: 2002-07-11 17:14:10
- Location: San Diego, CA
- Contact:
Re: Hang (or spinning beach ball) when insert .jpg
We did communicate privately with JLSchweitzer and figured out that the issue didn't have anything to do with the image itself, but rather a specific configuration of content in his document that triggered a particular layout bug.jessetc wrote:Did anyone ever get back to you?