Jump to content

Simulating command line parameters


LWC
 Share

Recommended Posts

Is there a way to simualte command line parameters instead of having to:

  • Compile the script.
  • Enter Windows' DOS prompt and run the script with paramerers and/or create a shortcut.
every time you want to run the script (if it can't run without parameters)?

$cmdlineraw can be re-assigned but it doesn't affect $cmdline, which is a non editable constant. Is there any way around it?

Thanks!

Link to comment
Share on other sites

  • Moderators

LWC,

If you are running your script in SciTE (at least in the full version you can get from here), you can use the <View - Parameters> menu selection to set up to 4 commandline parameters to test when you run. :x

M23

Public_Domain.png.2d871819fcb9957cf44f4514551a2935.png Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind

Open spoiler to see my UDFs:

Spoiler

ArrayMultiColSort ---- Sort arrays on multiple columns
ChooseFileFolder ---- Single and multiple selections from specified path treeview listing
Date_Time_Convert -- Easily convert date/time formats, including the language used
ExtMsgBox --------- A highly customisable replacement for MsgBox
GUIExtender -------- Extend and retract multiple sections within a GUI
GUIFrame ---------- Subdivide GUIs into many adjustable frames
GUIListViewEx ------- Insert, delete, move, drag, sort, edit and colour ListView items
GUITreeViewEx ------ Check/clear parent and child checkboxes in a TreeView
Marquee ----------- Scrolling tickertape GUIs
NoFocusLines ------- Remove the dotted focus lines from buttons, sliders, radios and checkboxes
Notify ------------- Small notifications on the edge of the display
Scrollbars ----------Automatically sized scrollbars with a single command
StringSize ---------- Automatically size controls to fit text
Toast -------------- Small GUIs which pop out of the notification area

 

Link to comment
Share on other sites

There's a bunch of ways you can make "default parameters", but here's a solution that can be easily applied to any script:

First use Ctrl+H to replace all instances of $CmdLine, with $aCmdLine, or any name you prefer.

Then add something like this to your script:

Global $aDefaultParams[3] = [2,"Param1","Param2"] ;set the default paramenters
If $CmdLine[0] Then ;if there are any parameters specified at all
    $aCmdLine = $CmdLine ;use the specified paramaneters
Else
    $aCmdLine = $aDefaultParams ;use the default parameters
EndIf
;$aCmdLine is used in the rest of the script.

I doubt this method has any advantages over the Shift+F8 option though.

Edited by Tvern
Link to comment
Share on other sites

I doubt this method has any advantages over the Shift+F8 option though.

The advantages lies in "when". In that you general better of using that way when your in initial Dev-stated. After your code has reached a certain stage(lets say production) it becomes less useful, and it becomes better to remove or minimize that part.

"Straight_and_Crooked_Thinking" : A "classic guide to ferreting out untruths, half-truths, and other distortions of facts in political and social discussions."
"The Secrets of Quantum Physics" : New and excellent 2 part documentary on Quantum Physics by Jim Al-Khalili. (Dec 2014)

"Believing what you know ain't so" ...

Knock Knock ...
 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...