fill attribute not working

HiI there

Consider this code sample
<timing clock="page">
    <par begin="0s" end="20s">
        <cue select="id('BTN01')" begin="//button[@id='BTN01'][@state:focused='true']"
            end="//button[@id='BTN01'][@state:focused='false']" fill="hold">
                <set style:border="8px solid fuchsia"/>
        </cue>
        <cue select="id('BTN02')" begin=0s"
            end="//button[@id='BTN02'][@state:focused='false']" fill="hold">
                <set style:border="8px solid fuchsia"/>
        </cue>
    </par>
</timing>



In the above code example ,"fill" works for second cue but not for the first cue.
Is this a bug in HDi simulator




Answer this question

fill attribute not working

  • Si B

    well.....actually i think i was not able to explain the sitaution ..so i go again

    <timing clock="page">
    <par begin="0s" end="20s">
    <cue select="id('BTN01')" begin="//button[@id='BTN01'][@state:focused='true']"
    end="//button[@id='BTN01'][@state:focused='false']" fill="hold">
    <set style:border="8px solid fuchsia"/>
    </cue>
    <cue select="id('BTN02')" begin=0s"
    end="//button[@id='BTN02'][@state:focused='false']" fill="hold">
    <set style:border="8px solid fuchsia"/>
    </cue>
    </par>
    </timing>

    In the sample code above......

    the first cue..whenever the BTN01 is focused, becomes active and border is
    changed as expected ............the problem is when the focus moves to some other button say
    BTN05.........the border is unset for BTN01,.. thus... fill="hold" does not appear to work.

    whereas for second cue.....behaviour is as expected,....


  • flash.tato

    i think i was not clear.

    i was referring only to the time duration from 0 to 20s.

    thus the style:border is not hold ( in between 0 to 20s) in first cue after the first cue has been activated.
    In other words, when the first cue gets activated , the style:border stays only for the time
    the end Xpath expression is false.it is not hold beyond that.(till the end of 20s period)




  • Thomas Pittman

    The par-block around these cues only goes from 0s to 20s. After these 20 seconds all cues inside (even these with fill="hold") get lost.


  • r3n

    Adding to the above post :

    the first cue has a begin Xpath expression and the second does not have one.



  • RMORAR

    Have you tried the () version I am fairly sure that @ is the wrong way at this time.

    Also since the first cue should never be set back to its initial value you could try using dur="0.5s" instead of the end attribute. This doesn't solve the source of this problem but it solves the result ;-)


  • NewbieElliott

    I think the problem is that you are checking for initial state, but not for the current. Try to use begin="id('BTN01')[state:focused()=1]" and end respectively formatted on this way.


  • crazyabtdotnet

    Turns out this is a known bug with HDiSim -- if you start a cue with an XPath expression then fill="hold" does not work. The Xbox should work properly though; just that HDiSim is kind of old these days...

    Work-around that will work both in HDiSim and Xbox is to put the PathExpression on the par:

    <par begin="PathExpression" dur="length>
    <cue select="PathExpression" dur="length" fill="hold">
    <whatever />
    </cue>
    </par>



  • ckob

    Thanks.

    Is there any chance of Microsoft releasing an update on HDiSim.



  • Idanle

    hi there

    I tried the '()' version , same result.

    Furthermore , you will agree that at least for state properties the '@' and '()' versions should be identical .

    Thanks



  • J. Clark

    try [state:focused()=true()] and [state:focused()=false()] instead of [@state:focused='true'] etc.

    The version with () uses the live dom, the version with @ uses the xmu as it is at load time or something like that.

    Also for performance issues you should use id('BTN01') instead of //button[...]

    As next when I look at the code I see two block with []. Since I am no Xpath master I don't know if this is allowed.


  • Mohsen Kokabi

    Yes, I believe there is a bug where the initial value of @state:focused doesn't get set on page load.

  • fill attribute not working