identifying button from script

identifying button from script

• Chris D Jones

  You need something like this in your markup:

  <cue begin="//button[state:actioned()]"
  end="defaultNode()[not(state:actioned())]">
  <event name="doAction" />
  </cue>

  and then in your doAction handler, you can use something like:

  evt.target.style.width = "500px";

  to set the width of the target element to 500 pixels.

  
  
  

• Derek at Potters Clay

  Where do you send the "doAction" event
  

• Lawrence 007

  One way would be to use the XML DOM APIs to get the element's parent and then check which of the childNodes has the same attributes.

  Note that you CANNOT use object identity (eg, "if (evt.target.parentNode.childNodes[0] == evt.target) {...}") because XML does not guarantee that nodes have the same identity; you need to check if the object is the same through some other mechanism. Usually, that would be through the id... so you would have to check x, y, width, height, etc. or whatever unique value you have. You might also be able to check if the state.actioned property was set, but that depends on timing.

  Any reason why you DON'T want ids They make life easier.

  
  
  

• L&amp;#225;szl&amp;#243; N&amp;#225;n&amp;#225;ssy

  Thanks,

  I'm working on something which has over 70 buttons, so giving them all an unique id, like 1, 2, 3, etc., takes some work. I thought it would be faster if I just could get the number of the #th button which was pressed.

  
  

• shankar ramachandran

  Yes the doAction was send from the markup (xpath), the script line was what I need. Is it also possible to know which button send the action, for instance the 4th button was pressed (without using id).

  
  
• identifying button from script