[Framers] Conditional Expression build crashing FrameMaker with Internal Errors

[Lin Sims]

I only just found it, so no. I have a bad habit of finding things like
this, though. When I was documenting software, the coders alternately loved
me and hated me. :)

And it looks as if I may be overthinking this in a BIG way. Apparently, I
was trying to be over-explicit.

For example, the expression I created that (would have) looked like this:

("A" or "External" or ("A" and "External")) and not (("A" and "Internal") or
"B" or ("B" and "External") or "TBP or "WriterNote")

Really only needs this:

"A" and not ("B" or "Internal")

And that even works if I have A and B and External (or A and B and
Internal) applied to some things.

Sheesh.

On Tue, May 10, 2016 at 10:16 AM, Steve Rickaby <
srickaby at wordmongers.demon.co.uk> wrote:

> At 09:43 -0400 10/5/16, Lin Sims wrote:
>
> >...but as soon as I try to enclose the entire "and not" clause in parens,
> >Frame crashes. The same thing happens if I enclose the second clause first
> >(it saves fine) and then try to enclose the first clause.
> >
> >I tried editing in the MIF, but the entire expression disappears from the
> >pick list when I do that.
> >
> >Any ideas on why Frame might be crashing? Any solutions? Is there a
> simpler
> >way of doing this? Do I even have the expression set up correctly?
> >
> ><frustrated>
>
> I guess the FrameMaker team should employ you as a tester ;-) My surmise
> is that you are pushing complex conditionals further than they have. Have
> you reported this as a bug? Looks like maybe a stack problem.
>
> --
> Steve
>



-- 
Lin Sims