Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
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
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Louie Landale, on Tuesday, October 21, 2003 12:16 PM

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
 14-Oct-2003 21:36
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Answer 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
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.