Milestones
List view
The WAMS Package API will allow for advanced packages. Packages made using this program will have the ability to request user input. These packages will also be able to be created easily through a GUI. Packages that are produced through this method will likely be produced into console applications. With this WAMS will receive a minor update adding input flag commands. Through this WAMS will also likely receive a package repository at which specific packages can be downloaded using the windows command line.
No due dateAdds beginner and professional mode to batchmain; this option can be found in the settings menu, and will have the ability to disable command tips. All paths shown in the command log will use the username of the current user instead of the global variable %USERNAME%. A zip file maker will be added, and so will a file formatting option.
Overdue by 5 year(s)•Due by December 7, 2020Adds an option to the settings menu that allows you to select whether the current file was made in WAMS or not. The WAMS manual will be improved upon. A info dialog will inform the user to select a file from the outputs folder of one of their projects. Null file cleanup will be added to batch files that have commands that use a null file.
Overdue by 5 year(s)•Due by November 23, 2020Allows inputs to be shown in the key log despite being inserted. Adds a settings menu to batchmain. Adds variable math functions to be performed. Adds a random number generator with range.
Overdue by 5 year(s)•Due by November 9, 2020A refresh button will be added to batchmain. The title command needs to always appear on the second line. Adds an else statement option. Adds jump sign instructions. Adds a project remover to the file maker.
Overdue by 5 year(s)•Due by October 26, 2020An @ sign is always placed in front of the RD command in batch. The file_maker does not remove the associated filehelper file when removing a file. All the slashes must face left in the commandlog.
Overdue by 5 year(s)•Due by October 12, 2020The trans command cannot be inserted. When inserting the run command to the first line it is placed above @echo off. Deletion names need to be improved as some of them are impossible to know. Non-alphanumeric keys cannot be used to name keys. Blank input commands are not shown in the command log or key log.
Overdue by 6 year(s)•Due by September 28, 2020Patches: Blank script insertion. This is when you use the insert command despite the script being blank; this can cause errors within the command log. Clear global variables. Sometimes when using the clear command global variables are removed from the key log. Even though the variables are removed from the key log, they are not actually removed from the project; this bug can temporarily be fixed by closing and than opening batchmain.exe. If string match bug. When selecting that one of the items being compared is a string the script crashes. This is caused by the quotations being placed around the string. The window is not large enough to view the entire insertion scale. The insertion scale will gain its own window. The WAMS menu icon does not set.
Overdue by 6 year(s)•Due by August 10, 2020•1/1 issues closed