☐ cool new feature
☑ could help many users!
☑ removes a „bug“
☐ nice to have
☐ nobody needs it
#myTop10_2023a
What inspired this wish list request?
Short:
Tables/Update destroys my source scripts. Stop it !!!
Long:
Many of the Platforms in the Tables menu provide the option Save Script to Source Table.
Is is an elegant way to save the command with all the settings as a Table Script Platform_Name Script.
There is even an auto-increment function which prevents Jmp from overwriting previous Table Script with the same name.
But there are two exceptions: Update and Concatenate.
As all the other functions, Concatenate saves the command script as a Table Script (name: source) to the output table.
Exception: If the option Append to first table is enabled, the main table is the output table - and NO script is saved (perhaps to prevent Jmp from over-writing an existing source Table script?)
For Update the main table is always used as output table. This function saves a table script with the current settings (name: source) to the main table and thereby: overwrites any existing source table script (!).
Table / Update - source script collision
What is the improvement you would like to see?
Concatenate and Update should follow the naming scheme of the other Table platforms.
i.e. save a script with the current settings to a Table Script with name Concatenate Script or Update Script.
An auto-increment feature should be used to prevent Jmp from overwriting existing scripts.
Why is this idea important?
The auto-generation of JSL source code is a great feature.
But over-writing an existing source code is more ham than good .
Fixing the issue will save users from losing their table source script.
The naming convention separates source scripts (name: source; was used to generate the data table) from Platform Scripts (name: Script; can be used to act on the current data table)