does not the "Exit for" without any condition cause the code to leave the loop inside the first round? Maybe you are not going to reach your problem anymore......
what I found was while this solved the fatal error it stopped copying the pagesetups.
So I did some troubleshooting and realized the the curps.dispose was the issue with it not copying the pagesetup
however I also discovered that if I removed the exit for and/or the curps.dispose I would get the fatal error again.
so in order for my code to work and copy the pagesetups without giving me the fatal error I had to stop/unload the curps without using curps.dispose and exit for.
so a long story somewhat short I did this:
using curps as plotsettings = new plotsettings(false)
This allowed me to copy the pagesetups as I wanted and not get a fatal error in the resulting code I removed all exit for's. What I learned from this is that you have to make sure that everything gets unloaded even the littlest thing still hanging out there can cause an error.
Hope this helps.
I understand that this thread is over a year old, and am not sure if posting here will still elicit a response.
If it does not, I will post again.
it seems that kenyon is saying that you havet to dispose of the variables as soon as you are done using it.
That means assigning the plot setting to a variable is out of question?
I am trying to write a function that simply returns the plot settings to the mother routine, based on the paper size the user picks in a form.
I am having no luck in preventing the autocad crash once it cycles through two or three of the page setups.
Intially, it cycled through all layout page setups.
And trying to get it to read any page setup that is not in a layout is out of the question.
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!