Topic: Freezing Xref Layers

[T.Willey]

Tom, what are your LAYFRZ options set to? Entity/Block/No nesting? Not sure if it'll help, but it may be worth a try.

OPTIONS! OPTIONS! We have options? 
Say it not true. Where?

Settings really.

Command: layfrz

Current settings: Viewports=Vpfreeze, Block nesting level=Block
Select an object on the layer to be frozen or [Settings/Undo]:

[TomREd]

I have tried all options and none of them made any difference....that lisp routine you spoke of that puts a string in front of all layer in the drawing, I am very intrested in.

[TomREd]

Allright boys and girls apperntly all i need was a cold morning a hot cup of coffee and fresh approach.

So this morning I created a new layer, made the new layer current and xrefed in the first section, then used the bind-bind command, after binding I exploded it. Well I wanted to check to see if the layer were freezable at this point so, I created a new drawing xrefed in the new file and to my amazement i was able to freeze layers. WOW!!! So to go on, I followed the same process step by step. and again to my amazement it still would freeze the layers....HOLY SHAT!!!

TO make a long story short I found a solution to my problem and its seems to be working....so I would like to thank all of you and have a wonderful rest of the day....as you can probably tell I am much ahppier this morning....


Oh yeah and most importantly----!!!! GO CARDS !!!

[Krushert]

I have tried all options and none of them made any difference....that lisp routine you spoke of that puts a string in front of all layer in the drawing, I am very intrested in.

As requested.  I snagged this routine from Afra-lisp site.  

TO make a long story short I found a solution to my problem and its seems to be working....so I would like to thank all of you and have a wonderful rest of the day....as you can probably tell I am much ahppier this morning....

So what was the issue and the solution?
Please don't leave us in suspense.

[TomREd]

There were several things I changed the second time around...first of all I believe all of this was caused by haveing a # symbol in the file name...I should have know better then to do that but hey everybody makes mistakes. The other difference was not binding all the xrefs at the same time, but i believe this was just a coincidence.

I think the main factor was the file name..I'm such a dummy, I looked at # symbol when i first did it and had a feeling that may have been it but never changed it.....oh well it works fine now.

[daron]

<ding-ding>

...first of all I believe all of this was caused by haveing a # symbol in the file name...

I just saw this topic and while reading, all I could think of was a drawing I worked on a couple of weeks ago, where the only thing that would not freeze with my regularly used routine, were layers that contained #'s in their names. Caused me a lot of grief it did, but that was what I learned; # symbols and lisp apparently don't get along. Do any of the programming guru's understand why?

[T.Willey]

I think it is the way the code is written.  Or it could be because the '#' character can be use as a wild card match, instead of the '#' character itself.

/guesses, waiting for a guru to come along.

[daron]

That would be my best guess too, but it's contained in a string. Hmm, must experiment... BBS (Be Back Soon.)

[daron]

Hmm. Curious. In the vlide I did this:
(setq a "343 # dfd")
It looks okay, so I inspect. It inspects okay, so I go to the command line and type !a. Lo-and-behold, it returns "343 # dfd". With all that a lisp should take that string and process it as requested, no? what gives here? Buggy program.

[T.Willey]

I would guess that the way the string is compared is the problem.  What does your part of the program look like when it is trying to freeze the layer?

Edit:
Did some testing with my routine.  I saved a drawings as 'Test#01.dwg', then xref'ed it into the current drawing.  I used my layer freeze command (posted above), and it worked fine.  Here is the output

Command: _LayFrez
Initializing...
 Select object on layer to be frozen [Undo]:
 Layer "Test#01|test" has been frozen.
 Select object on layer to be frozen [Undo]:

Then I binded it, as a bind, and here is the output

Command: _LayFrez
 Select object on layer to be frozen [Undo]:
 Layer "Test#01$0$test" has been frozen.
 Select object on layer to be frozen [Undo]:

[daron]

What does your part of the program look like when it is trying to freeze the layer?

Do you mean (command "freeze" a "")? Read on, otherwise, I'm not sure what you're asking.

Alright, tested a bit more. I changed the value of a to "343 \# dfd" and !a returns "343 # dfd". To be expected, so I type:
(command ".layer" "f" a "")
and get a return of:
No matching layer names found.

Grrr.

P.S. I also have tried this with vplayer, same results.

[T.Willey]

I think the command way will interpret it as a wildcard instead of the actually character.  Try coding it so that it isn't a command.  Here is an example of what I mean.

Command: (setq Str (value 8 ent))
"Test#01$0$test"

Command: (command "_.layer" "_Freeze" Str "")

No matching layer names found.
nil

Command: (vla-put-Freeze (vla-Item (vla-get-Layers (vla-get-ActiveDocument (vlax-get-Acad-Object))) Str) :vlax-true)

Where the last line works to freeze the layer.

[CAB]

Try this :

Code: [Select]

Command: (setq a "343 `# dfd")
"343 `# dfd"

Command: (command ".layer" "f" a "")

`  (reverse quote)   Escapes special characters (reads next character literally)

[T.Willey]

Try this :

Code: [Select]

Command: (setq a "343 `# dfd")
"343 `# dfd"

Command: (command ".layer" "f" a "")

`  (reverse quote)   Escapes special characters (reads next character literally)

Nice one Alan!  Learned something new today. 

[daron]

That's cool. Now the trick would be to have code that reads each string passed to it to find special characters, then place this before it. That or updating the working code with the vla-put-freeze should make it a bunch easier. I may have to do that. I think another job from the previous client is on the horizon and there's no telling what their layers will look like.