Community
It is very difficult for me to make meaningful sense from your description. For example, what is "Editor dialog"? Locking document does not necessarily prevent AutoCAD from crash, its necessity depends on what context your code runs in (Application or Document context).
You might want to describe what you want the code to do and show the code, and indicate which line of the code causes the crash (if you ever stepped through your code in debug, you should be able to tell that).
The method decorated with [CommandMethod(...)] should not have argument. As matter of fact, if the method is not static/Shared (as yours), if you run the command at command line ("IamCost"), AutoCAD will raise error (if the command method is static, having an argument would not raise error, but the argument would always be null). So, you need to remove the argument from the command method.
Then, you did not post code to show how the win form is displayed, and it is modeless or modal dialog. It is quite basic and important to understand the difference of modal and modeless dialog/window in conjunction with understanding code running context Application or document context.
Here are some critiques to your code:
1. You DO NOT show dialog/window, be it Win Form, or WPF, with Form[Window].Show()/ShowDialog() in AutoCAD .NET add-in. You should use overloaded Application.ShowModal[Modeless]Dislog[Window]() methods.
2. Creating new instance of floating/modeless form whenever user execute user command "SHOWCOSTFORM" is bad idea: if user keep hit "Enter", the command would repeatedly create/show new forms all floating on top of AutoCAD. I
3. Using modeless form needs extra care to coding, it is rather advanced coding skill. Do you really need the form to be modeless (floating)? Is the data showing on the UI related to the active document? If it is, what happens if the user switch to another document (because the form is modeless, so, user can change active document)? the data on the form obviously need to reflect the newly activated document, or you need to hide the form so user does not see data from previous document while facing a different document. Usually, when using modeless form out of necessity, the form should be instantiated as singleton object and live in the AutoCAD session once instantiated.
4. If user interaction with the form, such as button_Clcik, to execute your code that does something with AutoCAD, the code is executed in Application context, where you CANNOT call Editor.Command() (as you did in your code). To do something with modeless form is to use Document.SendTextToExecute() to excute your code wrapped in CommandMethod.
5. I do not see/understand why you need to use multiply nested transactions (up to 3 levels of nesting!) in your code
Anyway, assume you are sure you must use modeless form, here are the skeleton of code I put together out head with NotePad (thus, no syntax check):
This is the CommandClass:
public class Execution
{
private static Form_Main _form=null;
[CommandMethod("ShowForm", CommandFlags.Session)]
public static void ShowMainForm()
{
if (_form==null)
{
_form=new Form_Main()
}
Application.ShowModelessDialog(_form)
}
[CommandMethod("DoWork")]
public static void DoMyWork()
{
var doc=Application.DocumentManager.MdiActiveDocument;
var ed = doc.Editor;
// If you need get some user inputs from the form,
// for code execition, you can do it here
// var data1=_form.XXXXX;
// var data2=_form.YYYYY;
// Do whatever, including calling Editor.Command()
}
}As you can see, the form is declared as static. And following codes in the form's code behind do:
1. Make sure the form is not closed but invisible, when user tries to close the form, thus keep the form instance as singleton:
private void Form_Closing(object sender, FormClosingEventArgs e)
{
e.Cancel=true;
this.Visibile=false;
}
2. When user clicks the button to let your code do the work, it uses SendTextToExecute() to execute the command "DoWork", which could also be executed at command line, of course:
private void button_Trigger_Click(object sender, EventArgs e)
{
var doc=Application.DocumentManager.MdiActiveDocument;
doc.SendStringToExection("DoWork ",true, false, false);
}
I'd strongly suggest you to pay attention/study on the differences of using modeless or modal form. The issue you have is mainly because of showing the form as modeless and using the wrong method to show it (i.e. using Form.Show()).
Forums Links
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
