The behavior you describe is probably a result of the specific model, which may involve asynchronous behavior. Could you provide a sample project or screenshot (of the model)?
Regardless, you can probably handle this using a Boolean data element added to the display element containing the button, which is used as a flag, and checked by the button through an ancestor reference to ascertain whether it has already been pressed, and decide whether to execute the rest of the button's functionality.
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
