Closing a module does not discard unsaved changes

Hi,

I have just recently started using DOORS version 9.3.0.0

Whilst making changes in exclusive edit mode within a formal module, closing the module does not discard all unsaved changes.

I don't think "triggers" are being used withi nthe database so don't exactly know what is causing this to happen?

Any ideas?

Thanks
monde888 - Thu Aug 09 06:33:54 EDT 2012

Re: Closing a module does not discard unsaved changes
llandale - Thu Aug 09 16:57:23 EDT 2012

So you say perhaps: edit a module; change some value, then close and decline to save; that sometimes that change is there when you open the module? Are you in fact getting that prompt?

My guess is that something is saving the module before you close it.

-Louie

Re: Closing a module does not discard unsaved changes
monde888 - Fri Aug 31 07:21:55 EDT 2012

llandale - Thu Aug 09 16:57:23 EDT 2012
So you say perhaps: edit a module; change some value, then close and decline to save; that sometimes that change is there when you open the module? Are you in fact getting that prompt?

My guess is that something is saving the module before you close it.

-Louie

Hi,

Yes the behaviour is exactly that as you described.

I make some modifications, and when I close the module (WITHOUT saving), the module closes, with no prompt to ask me if I wanted to save the changes....and just before the window closes I can actually see the change bars goes from red to yellow to indicate the changes have been saved.

I can't find where there could possibly a setting that "autosaves" on module close.

Any ideas would be appreciated !!

Thanks

Re: Closing a module does not discard unsaved changes
llandale - Wed Sep 05 16:36:09 EDT 2012

monde888 - Fri Aug 31 07:21:55 EDT 2012
Hi,

Yes the behaviour is exactly that as you described.

I make some modifications, and when I close the module (WITHOUT saving), the module closes, with no prompt to ask me if I wanted to save the changes....and just before the window closes I can actually see the change bars goes from red to yellow to indicate the changes have been saved.

I can't find where there could possibly a setting that "autosaves" on module close.

Any ideas would be appreciated !!

Thanks

I've not see that. I see no "autosave" option. Something is saving your module, and that "something" is surely some DXL code; and that DXL code is likely a pre-close-module Trigger.

If you are a DB-Admin you can run this from the DXL window to stop triggers from running.

setTriggerState_(false)

Then re-try your test.

This may get you going on finding the offending trigger:


Trigger trg   

for trg in (current Project) 

do 
{  print name(trg) 
"\n" 
}

-Louie

Re: Closing a module does not discard unsaved changes
monde888 - Thu Sep 06 05:23:49 EDT 2012

llandale - Wed Sep 05 16:36:09 EDT 2012
I've not see that. I see no "autosave" option. Something is saving your module, and that "something" is surely some DXL code; and that DXL code is likely a pre-close-module Trigger.

If you are a DB-Admin you can run this from the DXL window to stop triggers from running.

setTriggerState_(false)

Then re-try your test.

This may get you going on finding the offending trigger:


Trigger trg   

for trg in (current Project) 

do 
{  print name(trg) 
"\n" 
}

-Louie

Hi Louie,

Tahnk you !!!!

Yes, setting the Triggers to false worked !!!

How do I make sure the DXL is run as soon as DOORS starts up??
When I ran your other bit of DXL to see what triggers there are, nothing came up, so really confused !

Thanks for your help

Ray

Re: Closing a module does not discard unsaved changes
llandale - Fri Sep 07 15:47:19 EDT 2012

monde888 - Thu Sep 06 05:23:49 EDT 2012
Hi Louie,

Tahnk you !!!!

Yes, setting the Triggers to false worked !!!

How do I make sure the DXL is run as soon as DOORS starts up??
When I ran your other bit of DXL to see what triggers there are, nothing came up, so really confused !

Thanks for your help

Ray

Perhaps in database:

for trg in database do

there is a " -T" command line switch to turn off running Triggers.

In a hurry, perhaps you can turn the following into printing useful info about found triggers:

g_bufResults += "\t>>>>>>>>TriggerDXL-" Label " '" (name(trg)) "': FoundIn '" FoundIn "' " stringOf(type(trg)) "-" stringOf(event(trg)) "-" stringOf(level(trg)) ":\n" dxl(trg) "\n"

-Louie