Qselect Select, Entire Drawing, while in Paperspace

[Anonymous]

Can someone clarify - what does "Entire Drawing" mean in Qselect?

When I do Qselect while in a Paperspace layout, checking Entire Drawing, it finds objects in the current layout paperspace only - it does not include modelview or other layouts - is this the intended result? 

(comparing with the FIND command, "Entire drawing" means ALL layouts AND modelview)

Thanks

[cadffm]

Entiry Drawing - in QSELECT mean "CURRENT SPACE" and find all Objects in current Space *(current Layout or Modelspace) which are not on frozen Layers.

*specified

[ВeekeeCZ]

Its not about layouts, but active object selection.

If you run the command with an active selection, you can select whether filter would be applied on current selection only (default) or the entire drawing = better wording would be "entire layout". You cannot make active selection across layouts.

See the HELP

[Shneuph]

ssget will do the entire drawing.  All layouts and model space.  If that's what you're looking for.

(sssetfirst nil (ssget "x"))

[Anonymous]

thanks for the suggestions - gets me half way there: 

the sssget manages to select and highlight all the appropriate objects in the real "entire drawing" but any subsequent operations performed on this selection set (such as "delete") effect only the objects.in the  "current space".  the other selected objects remain unchanged.  so we're back to square one.

any other ideas?

(btw it's strange the way "entire drawing" in qselect means something different from "entire drawing" in the Find command")

[jmartt]

[EDIT: SEE CAVEAT BELOW!!! (Post #10)]

I wanted to point out a benefit of this:

I used

(sssetfirst nil (ssget "x"))

to select everything, and then filtered the selection to Viewports using the Properties Palette. I was able to unlock/lock and set scales for the VPs through the Properties. 

That's what I wanted to do, so thanks very much for that.

But I was unable, as mentioned, to delete all the viewports...Delete only worked on the current layout.

[cadffm]

Autocad commands are always handle only objects in the current space, except some special commands.
So you can not move, rotate or delete objects in other spaces as the current one.

But you can do by programming your own functions.

In this case you need to set each layout current and delete the objects or use vlisp and vla-delete function.

But i prefer to learn (v)lisp from start to the end and not only some pieces, so you can help yourself if a problem ... *break*

Here is one example:
https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/deleting-selection-set-across-multip...

[jmartt]

Thanks for your efforts to help, @cadffm.

We've seemed to jump over to this from my original post: https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/change-scale-of-all-viewports/td-p/8...

[sharpl]

(sssetfirst nil (ssget "x"))

Thank you, it worked for me like a clock!!! 

[jmartt]

I think I stumbled on a big caveat for using this command the way I did three years ago. My annotative text was coming in at the wrong scale in paperspace whenever I used plan production (which is a Civil 3D feature that helps automate the layout of plan and profile sheets for road design). It was because the annotative scale of the paperspace was not 1:1. (Apparently, there's a paperspace "viewport". Others have stumbled on this. I'm not making it up.)

I think using that LISP routine above, and then isolating the viewports in the properties palette selected not only all of the viewports that look at modelspace, but also the paperspace viewports. Unlocking, changing the annotative scales, and locking again unintentionally changed the annotative scales of the paperspaces. You're not supposed to be able to do this. 

Here's where I started to figure this out:

https://forums.autodesk.com/t5/civil-3d-forum/annotative-text-in-paperspace-not-working/td-p/1080735...

[cadffm]

Hi

>>". My annotative text was coming in at the wrong scale in paperspace whenever I used plan production.

OT: You should not use annotation feature in paperspace,

as others stated too before.

>>"(Apparently, there's a paperspace "viewport". Others have stumbled on this. I'm not making it up.)

Yes it is, today this fact is a bit hidden from users eyes, but not completely.

(Thats why you have layeroverrides and vp freeze in paperspace too)

>>"I think using that LISP routine above, and then isolating the viewports in the properties palette selected not only all of the viewports that look at modelspace, but also the paperspace viewports."

Yes, you should better had used my codeline from the other post.

 Or for LT  use FILTER, Viewport and layer of your viewports, apply to ALL

[jmartt]

I wrote down what I did that worked here: https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/change-scale-of-all-viewports/td-p/8...

My text was annotative by style, by the way. I wasn't trying to "use annotation feature in paperspace". The text came in big because the annotation scale for that magic half-hidden paperspace viewport made it big. Once I used the trick -that I linked to above - and got the annotative scale of the paperspace VPs back to 1:1, text was generated at the intended height.

[cadffm]

>>"My text was annotative by style,"

No Text is annotative "by style" (not like i translate "by style"),

it is default setup of the current style, that's all.

>>"I wasn't trying to "use annotation feature in paperspace".

Yes, I know what you say and i understand and my "don't use annotation feature in paperspace" is just a generall a well-meaning council to keep the file in a clean way.

>" and got the annotative scale of the paperspace VPs back to 1:1, text was generated at the intended height."

1. To set paperspace back to 1:1 is a good step

2. but also my council is right, turn off your annotation property for paperspace objects.

    This way it would also works with another paperspace scale and added object scale are useless -> waste

   (sorry, i like to have clean drawing and good structures 😄 )