Originally Posted by RobertB
makes no difference
|
Originally Posted by RobertB
makes no difference
Robert,
Why have the VBA code autoload? Why not have the code in the acad.dvb and then execute the vba with a lisp loaded at the end of the Autocad initialization procedures? Will that resolve part of the problem?
Also, I have not reviewed or executed your code. So if this is a dumb idea, just ignore it.
If you have a technical question, please find the appropriate forum and ask it there.
You will get a quicker response from your fellow AUGI members than if you sent it to me via a PM or email.
jUSt
Good ideas, but ones that I already considered and tested. Placing the code in Acad.dvb avoids a load statement in the Acad.lsp file, true. However, it makes no difference in the issues that I'm trying to circumvent.Originally Posted by richardl.25628
Also, I figured it was easier for someone to remove the code if it was a separate .dvb file. (As a CAD Manager I know I'd prefer it if 3rd party stuff stayed out of my Acad.dvb!)
I'm almost ready to post a final update. I'm reduced to waiting for the command prompt to be available as AutoCAD is just too unstable that early in the game.
I need step-by-step issues from you, in order to understand what is going on at your end. It works as expected for Tod, vferrara, and I.Originally Posted by rhall.72202
Is that for making the "last active" current, closing "drawing1", both, neither?Originally Posted by RobertB
I almost asked if there was a time delay that could be set...
Making last active is not a problem. There is no way to get rid of Drawing1, since the code starts in Drawing1.
Autodesk thought that an Acad.dvb and AcadStartup procedure would avoid that issue, until I proved to them that is is a problem anyway. Maybe this will be fixed in the future. <sigh>
Here is the latest version (v1.2).
The biggest change was in the code to be placed in the Acad.lsp file. There was a few minor edits to the ReadSnapshot procedure.
Remember, AcadLspAsDoc should be set to 0!
Last edited by RobertB; 2007-09-12 at 10:52 PM. Reason: Removed old version
can not close because command still active error
Last edited by madcadder; 2005-08-16 at 06:56 PM.
I'm also getting the following error:
Code:Command: ze 'zoom ARX_ERROR: eNotThatKindOfClass ARX_ERROR: eNotThatKindOfClass ARX_ERROR: eNotThatKindOfClass ARX_ERROR: eNotThatKindOfClass Specify corner of window, enter a scale factor (nX or nXP), or [All/Center/Dynamic/Extents/Previous/Scale/Window] <real time>: e Regenerating model. ARX_ERROR: eNotThatKindOfClass ARX_ERROR: eNotThatKindOfClass ARX_ERROR: eNotThatKindOfClass ARX_ERROR: eNotThatKindOfClass Command: Zoom Extents Complete:
That's odd, as I'm not closing anything. Are you sure you don't have old stuff hanging around?Originally Posted by todw
BTW, your 2nd post shows some zoom commands being executed. Was that you, or some automation?