Topic: strange problem with events

[Jeff H]

In the BeginSave event have you tried checking DatabaseIOEventArgs.FileName and dropping out if file extension is 'sv$'?

[TheMaster]

after some day's of testing. I've came to a couple of things.

autocad 2009, no problems all works like it should.
autocad 2010, 2011, 2012 no problems all works like it should.


2013 works, until 1 document hits an autosave and the savehandlers are gone.

i know events have limitations, but it has been working for the last 5 years, why did it break in 2013.
the code hasn't changed much between the autocad versions.

Remember that this is not a full database app, i'm only doing a insert or update query to a sql database with 8 block attribute values.
there is no timing issue, or network delay.

i hope a fix is available, otherwise we will stay on 2012.

Most I know who are using customization have passed on AutoCAD 2013, because of many issues. That's what appens when new releases create more problems than they solve.

[sybold]

In the BeginSave event have you tried checking DatabaseIOEventArgs.FileName and dropping out if file extension is 'sv$'?

just tried it, same result. it magically gone

[sybold]

i've got a slim version running now with only printing savebegin and savecomplete in the commandline, not doing any other stuff. same problem.

[Jeff H]

In first example where does _Document variable come from, which Document is it pointing to?
How about posting a simple project that you can produce the problem with.

[trembre]

 I had the same issue - http://www.theswamp.org/index.php?topic=42961.msg481822#msg481822 - with AutoCAD 2011.

 The problem always arose using BeginSave when multiple drawings were open and an Autosave was fired off - for some reason the event handlers "disappear".  Despite targetting the apparently correct database for my handler as per the above thread, the problem persisted.  To get around this, I started intercepting saves by global command name, which does work well except for one issue - if the user tries to close a drawing without saving, AutoCAD offers them the option, and they click Yes, the code is bypassed. Will be trying the OnCommandWillStart option to see if that fixes it.

[Jeff H]

I had the same issue - http://www.theswamp.org/index.php?topic=42961.msg481822#msg481822 - with AutoCAD 2011.

 The problem always arose using BeginSave when multiple drawings were open and an Autosave was fired off - for some reason the event handlers "disappear".  Despite targetting the apparently correct database for my handler as per the above thread, the problem persisted.  To get around this, I started intercepting saves by global command name, which does work well except for one issue - if the user tries to close a drawing without saving, AutoCAD offers them the option, and they click Yes, the code is bypassed. Will be trying the OnCommandWillStart option to see if that fixes it.

If you read link posted by trembe Tony mentions problems adding handler multiple times and take a look at your DocumentedCreated and DocumentedActivated handlers.


Using 2013 with AutoSave and no problems.
Fires for each save and still fires after AutoSave has saved for multiple documents.

Code - C#: [Select]

1. using System;
2. using Autodesk.AutoCAD.Runtime;
3. using Autodesk.AutoCAD.ApplicationServices;
4. using Autodesk.AutoCAD.DatabaseServices;
5. using Autodesk.AutoCAD.Geometry;
6. using Autodesk.AutoCAD.EditorInput;
7. using System.IO;
8.  
9.  
10. // This line is not mandatory, but improves loading performances
11. [assembly: ExtensionApplication(typeof(AutoCAD_CSharp_plug_in1.MyPlugin))]
12.  
13.  
14. namespace AutoCAD_CSharp_plug_in1
15. {
16.  
17.  
18.     // This class is instantiated by AutoCAD once and kept alive for the
19.     // duration of the session. If you don't do any one time initialization
20.     // then you should remove this class.
21.     public class MyPlugin : IExtensionApplication
22.     {
23.  
24.  
25.         void IExtensionApplication.Initialize()
26.         {
27.             DocumentCollection docs = Application.DocumentManager;
28.             foreach (Document doc in docs)
29.             {
30.                 doc.Database.BeginSave += new DatabaseIOEventHandler(Database_BeginSave);
31.             }
32.  
33.  
34.             docs.DocumentCreated += new DocumentCollectionEventHandler(docs_DocumentCreated); ;
35.         }
36.  
37.  
38.         void docs_DocumentCreated(object sender, DocumentCollectionEventArgs e)
39.         {
40.            
41.             e.Document.Database.BeginSave += new DatabaseIOEventHandler(Database_BeginSave);
42.         }
43.  
44.  
45.         void Database_BeginSave(object sender, DatabaseIOEventArgs e)
46.         {
47.             if (Path.GetExtension(e.FileName) != ".sv$")
48.             {
49.                 Application.ShowAlertDialog(e.FileName);
50.             }
51.            
52.         }
53.  
54.  
55.         void IExtensionApplication.Terminate()
56.         {
57.             // Do plug-in application clean up here
58.         }
59.  
60.  
61.     }
62.  
63.  
64. }

[trembre]

Thanks Jeff - your code solves the problems I was having - my event only fires once, survives autosaves and works on close-save.  Now to figure out why - when I changed my code as per Tony and n.yuan's input, I wasn't too far off what you've written yet still had that issue...

[Jeff H]

Thanks Jeff - your code solves the problems I was having - my event only fires once, survives autosaves and works on close-save.  Now to figure out why - when I changed my code as per Tony and n.yuan's input, I wasn't too far off what you've written yet still had that issue...

I thought the code posted was following Tony and Norman's(n.yuan) advice.

[trembre]

It is, hence my confusion!  I'll have to dig out that code from my repository and compare it to yours.  While I got the point Tony and Norman were making at the time, I must have botched something else in the code... 

EDIT: After resurrecting that code turns out it does follow the same logic and does work.  :ugly:  Must've mixed up my dlls when I was testing - I'll get my coat.

[sybold]

it has been a while, been very busy.

this is great, i now realize what i was doing wrong.

all is working again