Way to go psychic Rudy, do you read tea leaves as well? And to think...someone said I need to re-read the original post... I knew something was amuck.... -- AUTODESK Authorized Developer http://www.Cadentity.com MASi
Glad you nailed it Dale. This thread certainly underscores why the use of globals is generally frowned upon. Your right Doug, I just thought that there might be something with the Startup Suite that was well known. Of course it's turned out to be a change made to another program that caused the error. Actually it exposed a bug that I've now fixed. Global variables ... yikes. Thanks again. Dale
Is it possible that something in your code crashes when it is loaded twice? You might want to use some conditional branching to prevent anything from happening on the second load: (if (not *YourAppWasLoaded*) (progn ;; contents of your existing .lsp file here. (setq *YourAppWasLoaded* t) ) )
It's getting wierder. I changed a var name on a hunch , recompiled and copied it to a users PC and the problem was fixed. I then copied the same file to another users PC and the problem still exists. If I remove the program from the StartUp Suite, start AutoCAD then manually load the program everything works splendidly on all users PC's. If I run the program with the source code through the VLIDE on all users PC's it works splendidly. Dale
Ho Luis. I was responding to the suggestion that problems associated with global variables can be remedied by compiling to a separate namespace. In my opinion that encourages careless programming and hides serious problems. I'm off-line until tomorrow <on my way to go see Aerosmith>, cheers all. porque? why? let me give you an example: how do you make it work to handle let say ODCL dialogs? in other words I am not saying to extra-populate the environment with globals et-al now explain it to me why is bad but in spanish 101 please... Gracias Miguel ....
Also, I just removed from all users Startup Suite, included (load "Bo.vlx") an thier acaddoc.lsp file and all is well. Questions: 1.) Why would this happen all of a sudden? I agree with the concences that something I've modified in other areas of the software had some effect but then: 2.) Why would the changes made fix the problem for one user who can still use the Startup Suite to load it but no others can. 3.) Why does it work well universally if manually loaded or loaded via acadoc.lsp? I apologize to all btw for the confusing way this thread has developed. It's broke, it's fixed!, oops it's only a little broke...etc. Best regards, Dale
1) why ask why? you wrote it. 2) We don't know how you setup your office to access each file. 3) Are perhaps accessing a autocad variable before it completely loads. As may have stated before, unless you're willing to share the code to see what exactly is occurring, we'll keep guessing... I've got a question for you, how many fingers am I holding up? A mechanic can't work on a car if it doesn't have an engine...nor can a bird flight if it doesn't have wings.
I've got a question for you, how many fingers am I holding up? Thats a good one, I like that. That makes sense and it's pretty too. LOL, I take your point Rudy, I geuss I was just trying to make a comment about how wierd it is that the same code behaves so differently on two different machines when loaded via the Startup Suite. I am perfectly willing to post the code but it's quite lengthy and it does run perfectly from the VLIDE. I'll struggle with it from here. Thanks again for your help though. Dale
Sorry about the humor...but you understand... We enjoy helping if we could...but we also understand if you don't want to share the code.
Thank you Luis, IT WAS GREAT <well spent coin> Don't worried my friend.... enjoy the concert!!! [the last one I went was to the YES 30th, here..in.SD]
A lot of look-a-likes, but no Liv "Dale Levesque" <dale at dynamicwindows.com> wrote in message Say hi to Liv for me if you see her Michael. : )
After reading this thread, why do people use the startup suite? Its so much simpler to have either the acad.lsp or Acaddoc.lsp control things. Then I can make the startup a little custom to various groups in our office by just checking a flag set in the registry. I would hate to constantly monitor the users startup suite. The only thing I use appload for is to unload a vlx once in a blue moon. Otherwise I have an LL function to load anything assuming its in the search path. If its not in the path, just browse for in explorer and drag in... I find the startup suite to be just another hidden thing to troubleshoot. I totally understand a non-lisper using it, but for those that do know lisp, is there some great thing the 'suite does that cannot be done with a startup lisp? thx James Maeding Civil Engineer/Programmer
The answer to your question is no. I too use acad.lsp and for those lsp routines that I use, I modify my acad.mnu to add them. But, to each their own way of doing things.
