![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DOORS 8.3 - close module w/o saving not working Topic Summary: Created On: 20-Dec-2007 00:33 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
OK, maybe someone else can duplicate this. I've been hammering at the last couple hours, and for the life of me I can not get the bool close (Module m, bool) function to work in 8.3.
I'm running the attached code from from test file in my User menu. If I make a change to the module, then attempt to run this script, which should close the module without saving, the module becomes invisible but is still opened and the changes are still present. If I were to reopen the module, DOORS just makes it visible and the changes are still there. Now if I make a change and attempt to close the module manually, I get the pop-up asking if I want to save. I click no and the module will actually close without saving. Can somebody please check and see if I'm not just really tired....lol. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
I just open a random formal module in a 8.3 database and could not reproduce this problem using the 8.3 client.
To be clear this is what I did specifically. 1) Open a random formal module in exclusive edit mode by hand 2) Made a single change to an object and did not save the changes 3) Ran the 3 line code from the DXL Interaction Window (copied and pasted the code) 4) Then I went to Tools -> Manage Open Modules to verify the module is closed and it was As an extra step, I reopen the module to check if the unsaved change was indeed unsaved. It was. Are you running the DOORS 8.3 client? ------------------------- pete.kowalski(at)motorola.com Edited: 20-Dec-2007 at 03:49 by Pete Kowalski |
|
![]() |
|
![]() |
|
Is the module being opened automatically from layout DXL in another module.
I have seen instances where the user closed without saving, opened again and the module appears as if it was never closed with red change bars. Unfortunately I could not reproduce the error consistently. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
I think Tony may be on to something.
Not a layout DXL that's causing it, at least not that I can tell I only have the one module opening. I have a trigger running in the project that runs a script prior to any module being opened. Basically the trigger runs a script that checks a few things and then requests some information from the user. After that the script will open the module using either the read or edit functions. After removing the trigger from the project, the issue seems to have gone away. The funny part is, is this worked fine in DOORS 8.1. I'm curious if maybe two instances of the module might be getting opened???? Is this possible? One from when the I actualy open the module and then one when the script opens the module. Sounds a little far fetched, but it's the only thing I can think of. Though I still haven't had my coffee this morning either. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
I just open a random formal module in a 8.3 database and could not reproduce this problem using the 8.3 client. To be clear this is what I did specifically. 1) Open a random formal module in exclusive edit mode by hand 2) Made a single change to an object and did not save the changes 3) Ran the 3 line code from the DXL Interaction Window (copied and pasted the code) 4) Then I went to Tools -> Manage Open Modules to verify the module is closed and it was As an extra step, I reopen the module to check if the unsaved change was indeed unsaved. It was. Are you running the DOORS 8.3 client? Yup running the 8.3 client.... ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Ahhh....OK I just noticed something.
When I have the trigger running. - Open the module. - Open "Manage Open Modules" - In the "References" column, it says there are two references for that module. When I remove the trigger. - Open the module. - Open "Manage Open Modules" - In the "References" column, it says there is only one reference for that module. Maybe my uncaffinated brain is working this morning???? Now how do I close a reference? ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
OK...Think I'm getting somewhere. Apparently with the trigger applied, DOORS creates a reference when you attempt to open the module, then the trigger creates another reference when it opens the module.
You can see this when apply the attached trigger. When this trigger is applied and you open a module, you'll see two references in the "Manage Open Modules" dialog. When the trigger is removed, and you open a module, only one reference is present. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Problem solved!!!!!
When I installed 8.3 I forgot to add the following switches to the target in the properties of the icon. -o READ_ONLY -O READ_ONLY These switches cause the modules to open in Read-Only by default, something we had done with 8.1. Apparently by doing this I've been able to rid myself of the extra reference and can now successfully close a module without saving. The other option was to make the trigger a post open trigger and make major modifications to the script. This is much easier as I need those switches in there anyway. On with my evaluation of DOORS 8.3!!!! God I hate having to document every upgrade Telelogic makes.....*lol* ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.