![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Switching from read-only to exclusive edit in DXL Topic Summary: Created On: 14-Oct-2003 20:56 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: There is a deployed Telelogic written call "setExclusive()" that sets the current module to exclusive. This command is invoked from the >>Edit Menu >> Edit Modes ... See also "setShared()" and "setReadOnly()". It works, but I've proved it creates an unfriendly environment for future complicated DXL. That is, a module opened "edit" is more stable to DXL than one improved via "setExclusive". But all you need to do is open the module for "edit", ignoring the fact that its already open for "read". This is a second or two slower than "setExclusive" but is overall superio. I believe, IIRC, that you need to "downgrade" a "shared" module before opening it exclusive. - Louie | |
![]() |
|
There is a deployed Telelogic written call "setExclusive()" that sets the current module to exclusive. This command is invoked from the >>Edit Menu >> Edit Modes ... See also "setShared()" and "setReadOnly()". It works, but I've proved it creates an unfriendly environment for future complicated DXL. That is, a module opened "edit" is more stable to DXL than one improved via "setExclusive".
But all you need to do is open the module for "edit", ignoring the fact that its already open for "read". This is a second or two slower than "setExclusive" but is overall superio. I believe, IIRC, that you need to "downgrade" a "shared" module before opening it exclusive. - Louie |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.