Frame 12 conditional text bug

Tue Jul 1 13:21:11 PDT 2014

The crashes I've mentioned happen in conditionalized documents - ours are structured, which may figure into this - and when you change the conditional settings to or from showing all conditions, FM crashes.  This has been in FM7, 9, and 10, which is as far as we've gone.

Often the mif wash will fix the problem, but sometimes not.  The issue seems to be odd conditioning that FM can't handle in structured docs, as the kind of conditioning that, when you change the conditions you create an invalid structure that freaks FM out.  Things like badly conditioned tables might do this, if you condition one cell structure element of the table accidentally.  We've also noticed it when someone, for example, deletes all text of a particular condition, as by deleting the condition, but there are invisible "remnants" of the condition left in the file.  Things like accidentally conditioned (or accidentally not removed) pilcrows.

Sometimes if we carefully go through the file and find every instance of a condition with all the conditions and text symbols turned on visible, we find something in the file we had missed before, and when we remove it manually, the file is "fixed".

Hope this can help you and others.

-- garyZ

From: rebecca officer [mailto:rebecca.officer at alliedtelesis.co.nz]
Sent: Tuesday, July 01, 2014 4:34 AM
To: framers at lists.frameusers.com; Zimmerman, Gary
Subject: RE: Frame 12 conditional text bug

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 >>>

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 the mif 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: framers-bounces at lists.frameusers.com<mailto:framers-bounces at lists.frameusers.com> [mailto:framers-bounces at lists.frameusers.com] On Behalf Of rebecca officer
Sent: Sunday, June 29, 2014 9:58 PM
To: framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>
Subject: Frame 12 conditional text bug

Hi everyone

I've just posted this on Adobe's bug tracker as https://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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20140701/0c365256/attachment.htm>