![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Saving a module Topic Summary: Created On: 15-Sep-2004 15:50 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have made some changes to a module through DXL - like creation of attributes. Now I try to save the module as follows:
save current At this point of time I am not prompted with a save dialog. So, I am assuming the changes have been committed. Now if I try to close the module graphically I am prompted with "Module has been modified and you will loose changes". do you want to save." dialog. If I say no the changes are not saved. My question is what is the role of save module command. And how can i save changes to a module programatically without prompting the user with a warning dialog. Thanks Babu |
|
![]() |
|
![]() |
|
Use the command
save current Module Your call to current is ambiguous, so I'm not sure what is "really" saved :-) Antonio. |
|
![]() |
|
![]() |
|
Thanks Antonio.
It worked. Babu |
|
![]() |
|
![]() |
|
You should routinely get a module handle when working on a module: mCurr = current. Then you can save(mCurr) or close(mCurr).
|
|
![]() |
|
![]() |
|
Can I second that Louie.
Never trust "current". There be dragons here. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Saving a module
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.