TheSwamp
CAD Forums => CAD General => Topic started by: theluck19 on February 11, 2013, 06:35:45 AM
-
Is it possible to this do to this via programming? I am having a tough time with grids being exploded frequently. :pissed:
-
Not sure about that but how about XREFs in a write protected folder?
-
IN the block file, call the block editor command for the current drawing and in the properties palette set the "Allow Exploding" value to "no".
This in affects locks the file with a padlock. Anybody with some brains can get around it but typical those people should with brains know the value of not exploding a grid. YMMV
-
Could you code a reactor to monitor for explode events of certain named blocks and either pop up an alert, or write to a network log file that you can monitor separately? They'll wonder at your omniscientness...
-
Could you code a reactor to monitor for explode events of certain named blocks and either pop up an alert, or write to a network log file that you can monitor separately? They'll wonder at your omniscientness...
Actually there is a phone home code around TheSwamp somewhere.
-
oooh, I need that
-
I need that too, desperately. I tried changing the value of explode to no in Block Editor, but some guys here are too wise to that.
-
If exploding things is not standard procedure, time for management to earn their money and play the bad-guy, and start yelling at people.
-
I meant the phone home code, LOL
found some of my custom blocks out 'in the wild' so to speak. Don't mind so much really, but part of my contract is that clients cannot share my stuff without written permission. I know its going to happen, but still nice to know how far they wander, lol.
-
I
If exploding things is not standard procedure, time for management to earn their money and play the bad-guy, and start yelling at people.
I did yell!!, but this is a big job and the guy is pretty new to CAD. The problem is his mistake caused a lot of rework to others. Now i've asked guys never to explode Blocks or Dims and if the really need to.. have a word with me. :realmad:
-
I can't find the original posting, but I believe the attached code was created by Luis.
It isn't perfect, but wil get you started.
-
i've asked guys never to explode... Dims and if the really need to..
There is absolutely no acceptable answer to the questions "Why are you exploding the dimensions?" or "Why do you have to explode the dimensions?"
-
Ooo, ooo, I got one.
"I didn't do it."
-
i've asked guys never to explode... Dims and if the really need to..
There is absolutely no acceptable answer to the questions "Why are you exploding the dimensions?" or "Why do you have to explode the dimensions?"
"The client says to."
-
Keep.lsp is a step in the right direction for me. Some tweeking and I can add it to the startup suite. Will let u know how thins go from here on!! :-) :-) Thanks!!
-
So... I am very interested in this idea as well.. Any luck on locking things down with a password since 6 years ago? :idea:
-
Management problems are best addressed with management solution, not technical workarounds.
-
Locks only keep honest people honest. Password protected blocks and entities do not exist for a reason.
-
We log critical dwg states to user editing sessions. When standards violations occur they can be swiftly identified and traced back to a designer. First infractions are met with friendly education, including restating "working to spec is a requirement of the role". Drawings that violate standards require extra time and money to process to an acceptable state. We keep people that help us keep our product competitive. Choose your path.
-
We log critical dwg states to user editing sessions. When standards violations occur they can be swiftly identified and traced back to a designer. First infractions are met with friendly education, including restating "working to spec is a requirement of the role". Drawings that violate standards require extra time and money to process to an acceptable state. We keep people that help us keep our product competitive. Choose your path.
This sounds like a very proactive pace to work...and a good approach.
-
Management problems are best addressed with management solution, not technical workarounds.
This ^^^^^^^^
... as Mark Kiker says "Don't let a management problem become a technology problem"