![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Current sensitive Commands Topic Summary: Created On: 23-Sep-2003 14:47 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Many DXL commands take the module as the parameter: ad = find(mod, NameAttr). Other commands presume the "current" module: filtering(on), flushDeletions(), create(attr), etc.
When using these commands you should routinely set the current module: current = mod or (current ModuleRef__) = mod flushDeletions(). This is because its often difficult to anticipate the current module in a DXL, since it changes at times; most notably when you OPEN another module but NOT when you TRY to open (an already open) other module. To support this you should routinely define a global variable at the top of most of your DXL, such as: Module g_mCurr = current; if (null g_mCurr){ack("run from open module)"); halt}. Thus, you can always set your "current" before using those sensitive commands. - Louie |
|
![]() |
|
![]() |
|
Thanks for the 'Top Tip'. Is is worth suggesting a separate forum for this sort of generally useful information to encourage others to share their pearls of wisdom in advance of a minor crisis from another user?
------------------------- Hazel Woodcock |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Current sensitive Commands
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.