Hi Dan,

Thanks for reporting this issue. We have logged a bug and will investigate more 
on this.
You can also log bugs on our external facing bug base.


Kunal Saini

-----Original Message-----
From: framers-boun...@lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Harding, Dan
Sent: Friday, May 30, 2014 1:31 PM
To: framers@lists.frameusers.com
Subject: Reproducible FM12 file corruption?

I've been seeing occasional wonkiness (yes, I know... it's a technical term) 
since upgrading from FM10 to TCS5 (FM12), but I think I have narrowed at least 
one of them down to the point where the behavior is reproducible on demand, but 
I'll be darned if I know what is triggering it.

Let's find out if it's just my installation/environment or if it affects others.

I'm running TCS5 under Windows 7, 64-bit Enterprise.

To try to eliminate character & paragraph format catalog issues and template 
anomalies, once I was able to reproduce the behavior, I tried doing the same in 
a generic FM file, and am also seeing the behavior there, so that's what I'm 
going to walk through. I've included screenshots of what I see along the way.

1. Create a new file using the default "Portrait" blank paper.


2. Copy in a few paragraphs of generic text (I use www.lipsum.com).


3. Save the file.

4. Place your cursor in one of the paragraphs.

5. In the Paragraph Designer, change the Spread to 1% and hit Enter to "Apply".


6. Save the file.

7. Press Ctrl+z to undo.



On my system, the margins change completely, as if room for side heads was 
added. In my main working file it also put footnotes in the middle of pages.

Also, it's not just any kind of change prior to a save and then undo that 
triggers the corruption. Simple text edits do not trigger it, however changes 
in the paragraph and character designers do. It's not just font attributes, but 
changing paragraph attributes and applying them, followed by a save and undo 
will also trigger the corruption. Changing the color of selected text via the 
tool palette, save, undo, will also trigger it.

It appears to be the sequence of (1) anything involving changing
*ATTRIBUTES* of text, (2) a save, and (3) an immediate undo, that triggers it. 
If I do the above steps without a save, the undo does not cause the corruption. 
It's as if reverting to a pre-save state makes FM go haywire.

Now that I know what triggers the page going nuts, I now know what to avoid 
doing. I would experience this periodically since I'm a save-monkey, and 
wouldn't know what the heck was going on.


Dan Harding
Technical Editorial Specialist
University of Illinois Tax School


You are currently subscribed to
To unsubscribe send a blank email to
Send administrative questions to listad...@frameusers.com. Visit 
http://www.frameusers.com/ for more resources and info.

End of framers Digest, Vol 104, Issue 2

You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
or visit 

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

Reply via email to