ForNotify...

[Anonymous]

I've looked throughout the ObjextARX Documentation but have yet to really find out why/how to use OpenMode.ForNotify.

What the advantages over ForRead and ForWrite? I figure they give extended power w/ handlers/reactors.

If someone would be so kind to give me an example requiring ForNotify, I would greatly/appreciate it.

[Anonymous]

I was wondering about this too.

I looked at the ObjectARX documentation for the following methods:
   Editor.UpgradeOpen()
   Editor.DowngradeOpen()
   Editor.UpgradeFromNotify()
   Editor.DowngradeFromNotify()

And I came across this website:
ttp://blog.sina.com.cn/s/blog_49a9ee140100ohrv.html

Looks to me that this is really more of a C++ ObjectARX thing for managing an object which could be accessed by different code at the same time.

I played around with opening objects for notify and found that you can easily cause crashes and corrupt the dwg so it couldn't be saved.

I think it might be best to steer clear of this one for .NET.

[Balaji_Ram]

A very simple explanation based on my understanding :smileytongue

More often we are interested in being an "observer" and reacting to events that happen within AutoCAD. In this case, the AutoCAD objects which we are interested in monitoring are "subjects". In this scenario, we will not need the use of "Notify" mode.

But, AutoCAD objects which act as subjects and have several observers, will open the "observers" that are database resident using the "Notify" mode.

So, in short we may never need to open it using the "Notify" mode unless our objects act as "subjects" and we have observers that are database resident.

[jeff]

ArtVegas,

Your link is directly from the documentation if you are using the arxmgd.chm try using the arxdoc.chm that includes arxmgd.chm and has alot more detail about objectarx that applies to .NET API