Author Topic: Attdisp Normal vs ON  (Read 9211 times)

0 Members and 1 Guest are viewing this topic.

T.Willey

  • Needs a day job
  • Posts: 5251
Re: Attdisp Normal vs ON
« Reply #15 on: April 29, 2010, 02:43:34 PM »
I don't see a way OOTB to change them once they are inserted, but you can change the ' attribute ' of the attribute definitions with ' battman '.  If you hit the ' edit ' button, the first tab is ' attribute ', and there is an ' invisible ' mode there that you could un/check.  I didn't see another way in '09.
Tim

I don't want to ' end-up ', I want to ' become '. - Me

Please think about donating if this post helped you.

MP

  • Seagull
  • Posts: 17750
  • Have thousands of dwgs to process? Contact me.
Re: Attdisp Normal vs ON
« Reply #16 on: April 29, 2010, 03:12:46 PM »
I know that I can set the visability status on entities, my problem is the company I got this from, I dont think they are smart enough to do this.  So mostly I am trying to figure out how they could have done this with out of the box autocad

Do not underestimate the ability of the garden variety idiot to use code found on the internet he cannot write and similarly does not understand, neither in construct nor use.
Engineering Technologist • CAD Automation Practitioner
Automation ▸ Design ▸ Drafting ▸ Document Control ▸ Client
cadanalyst@gmail.comhttp://cadanalyst.slack.comhttp://linkedin.com/in/cadanalyst

MP

  • Seagull
  • Posts: 17750
  • Have thousands of dwgs to process? Contact me.
Re: Attdisp Normal vs ON
« Reply #17 on: April 29, 2010, 03:15:15 PM »
Can it be done w/o code?

Not so much, unless you consider tools, like ET etc. to be created "w/out code".
Engineering Technologist • CAD Automation Practitioner
Automation ▸ Design ▸ Drafting ▸ Document Control ▸ Client
cadanalyst@gmail.comhttp://cadanalyst.slack.comhttp://linkedin.com/in/cadanalyst

David Hall

  • Automatic Duh Generator
  • King Gator
  • Posts: 4076
Re: Attdisp Normal vs ON
« Reply #18 on: April 29, 2010, 06:05:47 PM »
ET? I dont have ET as a command
Everyone has a photographic memory, Some just don't have film.
They say money can't buy happiness, but it can buy Bacon and that's a close second.
Sometimes the question is more important than the answer. (Thanks Kerry for reminding me)

Kerry

  • Mesozoic relic
  • Seagull
  • Posts: 11654
  • class keyThumper<T>:ILazy<T>
Re: Attdisp Normal vs ON
« Reply #19 on: April 29, 2010, 06:11:53 PM »
[WAG]

ET=ExpressTools
kdub, kdub_nz in other timelines.
Perfection is not optional.
Everything will work just as you expect it to, unless your expectations are incorrect.
Discipline: None at all.

MP

  • Seagull
  • Posts: 17750
  • Have thousands of dwgs to process? Contact me.
Re: Attdisp Normal vs ON
« Reply #20 on: April 29, 2010, 06:17:19 PM »
[WAG]

ET=ExpressTools

[●] correct
[ ] incorrect
Engineering Technologist • CAD Automation Practitioner
Automation ▸ Design ▸ Drafting ▸ Document Control ▸ Client
cadanalyst@gmail.comhttp://cadanalyst.slack.comhttp://linkedin.com/in/cadanalyst

David Hall

  • Automatic Duh Generator
  • King Gator
  • Posts: 4076
Re: Attdisp Normal vs ON
« Reply #21 on: April 30, 2010, 09:04:59 AM »
Express Tool, DUH!  I was thinking of the very old text editing command ET
Everyone has a photographic memory, Some just don't have film.
They say money can't buy happiness, but it can buy Bacon and that's a close second.
Sometimes the question is more important than the answer. (Thanks Kerry for reminding me)

MP

  • Seagull
  • Posts: 17750
  • Have thousands of dwgs to process? Contact me.
Re: Attdisp Normal vs ON
« Reply #22 on: April 30, 2010, 10:07:35 AM »
Couple drawings to demonstrate variable attribute properties.

ATTRIB_Example_1.dwg
ATTRIB_Example_2.dwg

Drawings are identical except for one thing.
Engineering Technologist • CAD Automation Practitioner
Automation ▸ Design ▸ Drafting ▸ Document Control ▸ Client
cadanalyst@gmail.comhttp://cadanalyst.slack.comhttp://linkedin.com/in/cadanalyst

David Hall

  • Automatic Duh Generator
  • King Gator
  • Posts: 4076
Re: Attdisp Normal vs ON
« Reply #23 on: April 30, 2010, 01:25:59 PM »
MP, you did that through code?  Very cool
Everyone has a photographic memory, Some just don't have film.
They say money can't buy happiness, but it can buy Bacon and that's a close second.
Sometimes the question is more important than the answer. (Thanks Kerry for reminding me)

MP

  • Seagull
  • Posts: 17750
  • Have thousands of dwgs to process? Contact me.
Re: Attdisp Normal vs ON
« Reply #24 on: April 30, 2010, 01:55:54 PM »
Yes sir + thanks.
Engineering Technologist • CAD Automation Practitioner
Automation ▸ Design ▸ Drafting ▸ Document Control ▸ Client
cadanalyst@gmail.comhttp://cadanalyst.slack.comhttp://linkedin.com/in/cadanalyst

Crank

  • Water Moccasin
  • Posts: 1503
Re: Attdisp Normal vs ON
« Reply #25 on: May 01, 2010, 04:02:59 AM »
You don't have to do that through code. Change the properties of the attribute with the BEDIT command and insert the block again.

Nb. I also think it's dangerous to change attributes so they are different from the block definition: If someone uses ATTSYNC on that block the result could be affecting other (overlooked) blocks as well.
So if you want to do this through code, your program should have to replace the original block with a unique copy (something like Autodesk did with dynamic blocks: after the properties have changed they are replaced with an unnamed version of that block).
Vault Professional 2023     +     AEC Collection

MP

  • Seagull
  • Posts: 17750
  • Have thousands of dwgs to process? Contact me.
Re: Attdisp Normal vs ON
« Reply #26 on: May 03, 2010, 03:21:37 PM »
I also think it's dangerous to change attributes so they are different from the block definition: If someone uses ATTSYNC on that block the result could be affecting other (overlooked) blocks as well.

I've used the technique successfully for more than double the years that I've been on this board. It's as dangerous as placing any info in the drawing users can modify or delete.
Engineering Technologist • CAD Automation Practitioner
Automation ▸ Design ▸ Drafting ▸ Document Control ▸ Client
cadanalyst@gmail.comhttp://cadanalyst.slack.comhttp://linkedin.com/in/cadanalyst

Krushert

  • Seagull
  • Posts: 13679
  • FREE BEER Tomorrow!!
Re: Attdisp Normal vs ON
« Reply #27 on: May 03, 2010, 04:53:12 PM »
I know that I can set the visability status on entities, my problem is the company I got this from, I dont think they are smart enough to do this.  So mostly I am trying to figure out how they could have done this with out of the box autocad

Do not underestimate the ability of the garden variety idiot to use code found on the internet he cannot write and similarly does not understand, neither in construct nor use.
Did somebody call my name?  :lol:
I + XI = X is true ...  ... if you change your perspective.

I no longer CAD or Model, I just hang out here picking up the empties beer cans

David Hall

  • Automatic Duh Generator
  • King Gator
  • Posts: 4076
Re: Attdisp Normal vs ON
« Reply #28 on: May 06, 2010, 09:12:04 AM »
MP, what language are you using to edit those attributes?  Its funny how things happen.  I asked this question last week or so, and yesterday the BIG boss came by and said they were having a meeting about the titleblock and blah blah blah.  Bottem line, I have to make it so the users cannot edit the first line of the title block.  So Im thinking make it constant , somehow using what you have described.

thanks
Everyone has a photographic memory, Some just don't have film.
They say money can't buy happiness, but it can buy Bacon and that's a close second.
Sometimes the question is more important than the answer. (Thanks Kerry for reminding me)

MP

  • Seagull
  • Posts: 17750
  • Have thousands of dwgs to process? Contact me.
Re: Attdisp Normal vs ON
« Reply #29 on: May 06, 2010, 10:07:32 AM »
Vanilla LISP (entmake or DXF modification). The applicable properties are read-only to ActiveX, so vla-* yada will not work, neither will VB(A). I'll post some applicable code when I can sneak some time.
Engineering Technologist • CAD Automation Practitioner
Automation ▸ Design ▸ Drafting ▸ Document Control ▸ Client
cadanalyst@gmail.comhttp://cadanalyst.slack.comhttp://linkedin.com/in/cadanalyst