Skip to main content
A
AndyEsslinger1-Visitor
1-Visitor
August 19, 2010
Question

EXTERNAL: FOSI - multiple levels of logic testing

  • August 19, 2010
  • 6 replies
  • 1308 views
Can you do it in 2 stages and set a flag in stage 1 then check it in stage 2?

<att logic="or">
<specval attname="foo" attloc="doc" attval="1">
<specval attname="foo" attloc="doc" attval="2">
<specval attname="foo" attloc="doc" attval="3">
<charsubset>
<savetext textid="foo.tdv" conrule="\true\">
</charsubset>
</att>
<att logic="and">
<specval attname="foo" attloc="#FOSI" attval="\true\">
<specval attname="type" attloc="doc" attval="\checklist\">
<charsubset>

</charsubset>
</att>


-Andy
\ / Andy Esslinger LM Aero - Tech Order Data
_____-/\-_____ (817) 279-0442 1 Lockheed Blvd, Mail Zone 4285
\_\/_/ (817) 777 3047 Fort Worth, TX 76108

    6 replies

    P
    ptc-9533431-Visitor
    1-Visitor
    August 19, 2010
    that might do it, I was trying to avoid having to create anything extra
    just for testing something I can already get to.

    > Can you do it in 2 stages and set a flag in stage 1 then check it in
    > stage 2?
    >
    > <att logic="or">
    > <specval attname="foo" attloc="doc" attval="1">
    > <specval attname="foo" attloc="doc" attval="2">
    > <specval attname="foo" attloc="doc" attval="3">
    > <charsubset>
    > <savetext textid="foo.tdv" conrule="\true\">
    > </charsubset>
    > </att>
    > <att logic="and">
    > <specval attname="foo" attloc="#FOSI" attval="\true\">
    > <specval attname="type" attloc="doc" attval="\checklist\">
    > <charsubset>
    >
    > </charsubset>
    > </att>
    >
    >
    > -Andy
    > \ / Andy Esslinger LM Aero - Tech Order Data
    > _____-/\-_____ (817) 279-0442 1 Lockheed Blvd, Mail Zone 4285
    > \_\/_/ (817) 777 3047 Fort Worth, TX 76108
    >
    >
    E
    ebenton1-Visitor
    1-Visitor
    August 19, 2010
    So, having 3 atts with two specvals each, with all 3 atts doing the same thing wouldn't work?

    <att>
    <specval attname="type" attval="\checklist\">
    <specval attname="foo" attval="1">
    [do thing number 1]
    </att>
    <att>
    <specval attname="type" attval="\checklist\">
    <specval attname="foo" attval="2">
    [do thing number 1]
    </att>
    <att>
    <specval attname="type" attval="\checklist\">
    <specval attname="foo" attval="3">
    [do thing number 1]
    </att>
    P
    ptc-9533431-Visitor
    1-Visitor
    August 19, 2010
    Then add the other known value of type=manual along with the third test I
    know have to test and things just start to grow to an unmanagble list of
    values. My type actually has about 10 values right now, not sure if I need
    to do something special for each one, but they are specified by name. So
    I'm now trying to set up the FOSI to allow for these possible variations.

    The programmer in me wants to keep it simple and neat and have a single
    statement that covers the same situation

    > So, having 3 atts with two specvals each, with all 3 atts doing the same
    > thing wouldn't work?
    >
    > <att>
    > <specval attname="type" attval="\checklist\">
    > <specval attname="foo" attval="1">
    > [do thing number 1]
    > </att>
    > <att>
    > <specval attname="type" attval="\checklist\">
    > <specval attname="foo" attval="2">
    > [do thing number 1]
    > </att>
    > <att>
    > <specval attname="type" attval="\checklist\">
    > <specval attname="foo" attval="3">
    > [do thing number 1]
    > </att>
    >
    P
    ptc-19080751-Visitor
    1-Visitor
    August 19, 2010
    One thing: The #FOSI test must be in a pseudo-element in order to correctly
    evaluation foo.tdv. #FOSI doesn't work in the same e-i-c that foo.tdv is saved
    to. A usetext is needed in the charlist to call the pseudo-element.
    Placemnt=after is probably needed to ensure the pseudo-element is processed
    after the att. Example: usetext
    source="<test-foo-checklist.psu>,</test-foo-checklist>" placemnt="after".

    Suzanne Napoleon
    SuzanneNapoleon@FOSIexpert.com
    "WYSIWYG is last-century technology!"


    P
    ptc-9533431-Visitor
    1-Visitor
    August 19, 2010
    So it sounds like I'm stuck with defining psuedo-elements for every
    combination I come up with. I was hoping Andy's trick would do it, at
    least everything would be in the same eic.

    Paul, good news on the extension but I'm stuck with 5.2 at the moment,
    I'll have to check though.

    thanks

    ..dan

    > One thing: The #FOSI test must be in a pseudo-element in order to
    > correctly
    > evaluation foo.tdv. #FOSI doesn't work in the same e-i-c that foo.tdv is
    > saved
    > to. A usetext is needed in the charlist to call the pseudo-element.
    > Placemnt=after is probably needed to ensure the pseudo-element is
    > processed
    > after the att. Example: usetext
    > source="<test-foo-checklist.psu>,</test-foo-checklist>" placemnt="after".
    >
    > Suzanne Napoleon
    > SuzanneNapoleon@FOSIexpert.com
    > "WYSIWYG is last-century technology!"
    >
    >
    >
    P
    ptc-19080751-Visitor
    1-Visitor
    August 19, 2010
    I don't think a separate pseudo-element is needed for each #FOSI test. I think
    all the atts could be in the same pseudo-element.

    Suzanne


    Terms & ConditionsAccessibility statement