![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Documentation on trigger status constants? Topic Summary: Created On: 20-Sep-2006 16:25 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I looked at the DXL reference manual. While it outlines the trigger status constants (trigPreConPass, trigPreConFail etc.) but does not explain the meaning of each of these triggers. Is there somewhere they have been explained? I would appreciate it if you could let me know. Thank you.
Regards, Pranav |
|
![]() |
|
![]() |
|
'Pre' event triggers allow the trigger code to disallow the event. A pre-attr-save trigger is allowed to check the proposed input and not save the attribute if needed.
Well, you express your desire in 'pre' event triggers by setting either trigPreConPass or trigPreConFail. You can set them anytime during the code, the last one set has precedent when the trigger code ends. trigPreConFail means disallow the subsequent event. Don't know what trigRunOK and trigError are for, but I imagine that trigError has the same effect as trigPreConFail, and trigRunOK has the same effect as trigPreConPass. Give it a try and let us know. - Louie BTW, 'post' triggers let you react to an event after it happens, such as opening a module. |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Documentation on trigger status constants?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.