Hi Gary
That's a good idea, thanks. We'll try it. Apart from anything else, it'll be
really interesting to see if MIF files show the same bug.
About those crashes you mentioned, are they on Frame 12? We're seeing a lot of
crashes too, but we haven't figured out a pattern to them yet. We're not
exactly fans of Frame 12 right now!
Cheers
Rebecca
>>> "Zimmerman, Gary" 06/30/14 5:14 PM >>>
<!--/* Font Definitions */@font-face{font-family:Calibri;panose-1:2 15 5 2 2 2
4 3 2 4;mso-font-alt:"Times New
Roman";mso-font-charset:0;mso-generic-font-family:swiss;mso-font-pitch:variable;mso-font-signature:-520092929
1073786111 9 0 415 0;}@font-face{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4
2 4;mso-font-alt:"
Verdana";mso-font-charset:0;mso-generic-font-family:swiss;mso-font-pitch:variable;mso-font-signature:-520081665
-1073717157 41 0 66047 0;}@font-face{font-family:"Segoe UI";panose-1:2 11 5 2
4 2 4 2 2
3;mso-font-charset:0;mso-generic-font-family:swiss;mso-font-pitch:variable;mso-font-signature:-520084737
-1073683329 41 0 479 0;}/* Style Definitions */p.MsoNormal, li.MsoNormal,
div.MsoNormal{mso-style-unhide:no;mso-style-qformat:yes;mso-style-parent:"";mso-margin-top-alt:auto;margin-right:0in;mso-margin-bottom-alt:auto;margin-left:0in;mso-pagination:widow-orphan;font-size:12.0pt;font-family:"Times
New
Roman","serif";mso-fareast-font-family:Calibri;mso-believe-normal-left:yes;}p.MsoBodyText,
li.MsoBodyText,
div.MsoBodyText{mso-style-noshow:yes;mso-style-priority:99;mso-style-link:"Body
Text
Char";mso-margin-top-alt:auto;margin-right:0in;mso-margin-bottom-alt:auto;margin-left:0in;mso-pagination:widow-orphan;font-size:12.0pt;font-family:"Times
New Roman","serif";mso-fareast-font-family:Calibri;}a:link,
span.MsoHyperlink{mso-style-noshow:yes;mso-style-priority:99;color:blue;text-decoration:underline;text-underline:single;}a:visited,
span.MsoHyperlinkFollowed{mso-style-noshow:yes;mso-style-priority:99;color:purple;text-decoration:underline;text-underline:single;}p{mso-style-name:"Normal
\(Web\)\,ZimsEmail";mso-style-noshow:yes;mso-style-priority:99;mso-style-qformat:yes;mso-margin-top-alt:auto;margin-right:0in;mso-margin-bottom-alt:auto;margin-left:0in;mso-pagination:widow-orphan;font-size:12.0pt;font-family:"Times
New
Roman","serif";mso-fareast-font-family:Calibri;}span.BodyTextChar{mso-style-name:"Body
Text
Char";mso-style-noshow:yes;mso-style-priority:99;mso-style-unhide:no;mso-style-locked:yes;mso-style-link:"Body
Text";}span.EmailStyle20{mso-style-type:personal-reply;mso-style-noshow:yes;mso-style-unhide:no;mso-ansi-font-size:10.0pt;mso-bidi-font-size:11.0pt;font-family:"Courier
New";mso-ascii-font-family:"Courier New";mso-hansi-font-family:"Courier
New";mso-bidi-font-family:"Times New
Roman";color:maroon;font-weight:bold;mso-bidi-font-weight:normal;font-style:normal;}span.SpellE{mso-style-name:"";mso-spl-e:yes;}.MsoChpDefault{mso-style-type:export-only;mso-default-props:yes;font-size:10.0pt;mso-ansi-font-size:10.0pt;mso-bidi-font-size:10.0pt;}@page
WordSection1{size:8.5in 11.0in;margin:1.0in 1.0in 1.0in
1.0in;mso-header-margin:.5in;mso-footer-margin:.5in;mso-paper-source:0;}div.WordSection1{page:WordSection1;}-->p.MsoNormal{margin-left:3.0pt;}
Hi Rebecca,
Have you tried working in .mif files instead of .fm files and only saving to
.fm when you're done for the day?
When we have some conditional text problems that crash FM, a mif wash of the
files often helps, and sometimes fixes the problem. If yours is a bug, then the
mif wash won't help, because as soon as you're back in .fm you'll hit the bug
again. But maybe if you save the file as a mif, then work in themif as much as
you can, and only save as an .fm doc at the end, it would at least save you
some time during development.
-- garyZ
From: [email protected]
[mailto:[email protected]]On Behalf Of rebecca officer
Sent: Sunday, June 29, 2014 9:58 PM
To: [email protected]
Subject: Frame 12 conditional text bug
Hi everyone
I've just posted this on Adobe's bug tracker
ashttps://bugbase.adobe.com/index.cfm?event=selectBug&CFGRIDKEY=3783041 but
wanted to see if anyone else is seeing it too.
We have unstructured FM 12 files that use Expressions to choose what
conditional text to display. We also use text insets, especially as TOCs in
chapters. When we update the text insets, conditional text displays that should
be hidden according to the Expression. This means our documents suddenly
display extra text!
Our text insets are set to update automatically when files open, so opening a
file is often enough to trigger this bug.
Fortunately, we found a workaround: The display becomes correct if we turn the
Expression off and then on again. For example, if we set the Show/Hide
Conditional Text dialog to Show All and click Apply, then set it to show as per
the desired Expression and click Apply, it'll display correctly. Until the next
time we do something radical like opening the file.
The workaround is a lot better than nothing, but it means we have to keep
changing the Show/Hide Conditional Text dialog, across books of thousands of
pages. It's slowing us down enough to drive us batty.
Cheers
Rebecca
NOTICE: This message contains privileged and confidential
information intended only for the use of the addressee
named above. If you are not the intended recipient of
this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it.
If you have received this message in error please
notify Allied Telesis Labs Ltd immediately.
Any views expressed in this message are those of the
individual sender, except where the sender has the
authority to issue and specifically states them to
be the views of Allied Telesis Labs.
NOTICE: This message contains privileged and confidential
information intended only for the use of the addressee
named above. If you are not the intended recipient of
this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it.
If you have received this message in error please
notify Allied Telesis Labs Ltd immediately.
Any views expressed in this message are those of the
individual sender, except where the sender has the
authority to issue and specifically states them to
be the views of Allied Telesis Labs.
_______________________________________________
You are currently subscribed to framers as [email protected].
Send list messages to [email protected].
To unsubscribe send a blank email to
[email protected]
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to [email protected]. Visit
http://www.frameusers.com/ for more resources and info.
