![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL triggered by attribute edit event Topic Summary: Created On: 6-Dec-2005 08:56 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello @ all! ------------------------- Greetings,<BR>Oliver<BR><BR><BR>Oliver Roepke<BR>Axis Engineering AG, Munich |
|
![]() |
|
![]() |
|
You can trigger when you select a new object but cannot trigger when you begin to edit an attribute. The best you can do is trigger when he's done editing the attribute. Such a pre-save-attribute trigger may do the following: Read the user's input and translate it as best as it can into the options you define. Present the options with the user's current selections selected. When he's done, save the attribute value.
Users can attempt to type in what they want, but may have to simply add a space to the end of the value in order to trigger the trigger. The "AttrDef ad = attrdef(current Trigger)" command should find which attribute is being saved. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
DXL triggered by attribute edit event
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.