![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Module owner of an AttrDef Topic Summary: Created On: 11-Nov-2003 19:15 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Beware of DXL Triggers - thar be dragons within ![]() Assuming that the firing of an attribute trigger means that the containing module is open, then you might be able to do a do an outer loop on all open modules and an inner loop on all AttrDefs in each module trying to do an '==' on each AttrDef to attrdef(current Trigger). Not sure if that would work though... Another option would be to create module-specific instances the attribute trigger for each module. Then you could use the 'Module module(Trigger)' or 'string stored(Trigger)' to determine the containing module. Good luck. | |
![]() |
|
I've got an "AttrDef" type variable and want to figure out the name or handle of the module that actually owns that AttrDef. Is there some sort of "mod = module(ad)" command?
I'm aware that to get the AttrDef in the first place I need the module handle; except that in my case I'm getting the AttrDef via the "attrdef(Current Trigger)" command, and don't know how to figure out which MODULE owns the attribute (could be in the "current" module, but it also may be in the link module). - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Module owner of an AttrDef
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.