Topic: Global Page Setups

[Dommy2Hotty]

Is it possible to have a set of standard page setups for plotting defined in AutoCAD itself?  I understand I can import from another drawing, or start with a template, but a lot of our work is changes to an existing plan.  It just gets time consuming to import them.

[CAB]

Drawing Name "PageSetups.dwg" with all your required set ups.

Button

Code: [Select]

^C^C.-PSETUPIN "PageSetups.dwg" "*"

How hard is that?

CAB

[Dommy2Hotty]

Not hard at all!! didn't know about that command...spank you very much....you never fail to help me out...


EDIT: Okay, one more thing...is there a command to clear all page setups first, so that it will add the ones from the PageSetups.dwg and have those as the only ones in the drawing?

[ronjonp]

this works for me:

Code: [Select]

;;  Function to delete all user plot set ups
(defun c:Del_Pagesetups (/ curdwg pslayout x)
  (vl-load-com)
  (setq
    curdwg   (vla-get-ActiveDocument (vlax-get-Acad-Object))
    pslayout (vla-get-Layout (vla-get-PaperSpace curdwg))
  ) ;_ end of setq
  ;; Call RefreshPlotDeviceInfo before GetPlotDeviceNames
  (vla-RefreshPlotDeviceInfo pslayout)
  (vlax-for x (vla-get-Plotconfigurations curdwg)
    (vla-delete x)
  ) ;_ end of vlax-for
) ; End Plot_config_list
(c:Del_Pagesetups)

Code: [Select]

^C^CDel_Pagesetups;^C^C.-PSETUPIN;C:/.../PageSetups.dwg;*;^C^C.plot;

Ron
 

[JCTER]

Warning: Necro-bump.

I'm looking to populate our standard benefits to include some named page setups.

I wish that I could simply have page setups saved to an external file like .pc3 files.  I don't understand why that is not possible, or already in existence.  Maybe it has been since this thread.  If so I am very open to suggestion.

Concluding question and main point:  Is the above recommendation still the most efficient and/or typically preferred method of implementing saved page setups?

I have everyone creating drawings from the same setup, now, but like Dommy noted, we as well often are working with other's drawings and modifying them, so simply saving the page setups in our template won't tackle -all- situations.

Redefining the 'plot' command in our enterprise CUI to include a macro to import page setups is the last resort, but if it's effective, I don't mind.