I have tried almost the same thing - the only way that works would be to add the script to the scripts menu and launch it using mcr from there. Basically it works but as soon as the menu changes the mcr stops working (or would launch a wrong script).
(The adding to script menu tags are stored in powerlogic.ini, so that's another file to manage, as you mention)
We are now up to 5 files to manage, but it does work...
You can start a Script at program startup this way as well:
Edit the "Target" line of the shortcut used to start Logic, to read something like this:
C:\MentorGraphics\9.0PADS\SDD_HOME\Programs\powerlogic.exe /s"C:\PADS Projects\Scripts\MyScript.BAS"
I use this method to run a script for Layout, but never actually tied it for Logic.
When I do this with layout (v9.4) is just opens the script for editing in the Output Window. It does NOT actually run the script.
Are you trying to run a "script" (.bas) or a "macro" (.mcr)? Macros open in the Output window, I've never seen script run/open there.
Use /m for .mcr macros at startup.
Sorry, that needs to be a capital "M".
Is there a published list of switches for powerpcb.exe?
1 of 1 people found this helpful
look in the HTML version:
Opens the specified design file when you start PADS Layout. Type the full folder path and file name. Use quotation marks for folders or file names with spaces.
Example: “C:\PADS Projects\Samples\preview.pcb”
Restriction: Do not use a forward slash ( / ) before the file name in the command line.
( [ ] represents optional text.)
Opens the Basic Media Wizard. Use the Basic Media Wizard to start recording a session log or to convert the previous session log to media that can be replayed by Basic Log Test. To create session media files for the current PADS Layout session, use the BMW modeless command.
To use the BMW command line switch, type /BMW or /BMW=xx, where xx is your initials, in the command line. Note the capitalization.
This option is associated with another modeless command, BLT. BLT is the Log Test; it finds and runs the session media created by BMW to play back a recorded PADS Layout session.
See also: Typing Modeless Commands
Runs the integrity test on every file open.
Opens the last file you had open when you start PADS Layout.
Runs the specified macro in the default macro file. For example, to run the macro MyMacro, type /mMyMacro.
Specifies the file to use as the default macro file. For example, to run the macro MyMacro contained in the file user1.mcr, type /Muser1.mcr /mMyMacro. Note the required capitalization.
Requirement: Macros must be in the \PADS Projects folder.
Starts PADS Layout without displaying the splash screen that includes copyright information.
Disables true layer associations. When you use Flip Side, the layer attributes will not move to the new layer with the component. Type /NTL to disable true layer associations. Note the required capitalization.
TrueLayer is enabled by default and moves mask layer definitions with a part that is placed on the opposite side of the board. It also correctly plots paste masks of documentation-level pad shapes in CAM. The layer that the definitions move to is set in the Component Layer Associations dialog box.
Starts a Basic script when you start PADS Layout. Use quotation marks for file names with spaces.
Example: “/sC:\PADS Projects\Samples\Scripts\Layout\Unsupported\Attributes to Excel.bas”
I'm trying to run a .bas script.
...then lower case "s".
If it's opening up in the editor and not running then you most likely have an error in the script.
I just checked it in a VX2.2 install and it still works.
My bad, I did actually have a syntax problem. The script I am pointing to launches a custom Toolbar that I open EVERY time I work on a layout.
The script runs if I click a shortcut or open an empty instance of PADS Layout but I can't open an actual layout design and force the application to run that .bas script.
Is there a section of the powerpcb.ini file where I can point to the path and file name of the script and have it open when PADS Layout opens?
Or do I have to wait until I move up to V2.4 to use the startup.ini file?
It should run automatically if you correct all the errors.