![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: shareable edit -> downgrade and shareable edit again Topic Summary: Created On: 14-Jun-2007 14:20 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have following problem with switching between different edit modes via dxl:
1. The module is open in shareable edit mode. One section is locked. 2. DXL downgrades the module using the downgrade command. 3. After some other actions while the module is open read only DXL opens it shareable edit again. The command used is "share("Modname", true)". Unfortunately the module changes to exclusive edit !!! How can I open the module in shareable edit? Regards Darius |
|
![]() |
|
![]() |
|
Way back in v5, the following commands sometimes caused corruption of the DOORS environment such that no DXL would run. Haven't seen that problem lately. These are the calls used by the Edit menu >Open commands:
setReadOnly() setExclusive() setShareable() They obviously work on the current module. They may be easier than downgrade followed by shared. Using downgrade(mod) may cause a problem if you have a locked modified section. I suppose DOORS will prompt you to save it. |
|
![]() |
|
![]() |
|
Louie
thanks for your answer. I use DOORS v7.1 so I do not expect problems occured in v5 in the main. The commands you propose are not available in DOORS manual. Are they not documented i. e. hidden? I do not like to use hidden commands for to-be compatibility reasons. Regards Darius |
|
![]() |
|
![]() |
|
These are not undocumented perms nor commands, they are functions written by telelogic ..err.. actually by QSS way back when. I found them while browsing the 'formal.dxl' file (or whatever) that defines the menues in a formal module, the 'Exclusive' command invokes function setExclusive().
These 3 commands are encrypted somewhere. My old testing showed convincingly that they are NOT the same as some sort of downgrade-open sequence, something we DXL nerds have no doubt written at some time or another. Other than that, I really don't know how they work. - Louie |
|
![]() |
|
![]() |
|
I would say that using SetReadOnly(), setShareable() and setExclusive() is pretty safe - as far as I know these haven't changes for years and are unlikely to now. As Louie says, using these is far easier that doing the downgrade, open stuff youself. Although they only work on the current module.
For those who are interested, the attached shows you how these funtions work. Note that my examples do not assume the current module, but take a parameter. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
What's inplaceEditOff?
|
|
![]() |
|
![]() |
|
My apologies, I didn't realize that this perm was not documented. When you are editing an object, i.e. you have the curser in the Object Text or an attribute etc it is called in place editing.
bool inplaceEditOff(Module m, bool keepChanges) The function inPlaceEditOff turns off the inplace editing - same as clicking elsewhere in the GUI or hitting Ctrl-M. If the keepChanges parameter is true then edits are preserved, otherwise they are lost (same as hitting ESC key in the GUI). Try this. Edit an object's text and leave the curser visible in the text (i.e. you are still editing the object). Run inplaceEditOff(current Object, true) and see that the change bar for the object turns red and your changes are still there. Do the same again, but this time run inplaceEditOff(current Object, false). Note that your changes are gone and the change bar is not red. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.