Record Subset action via logWhen I go to Tables/Subset and then in the platform, when I click on OK, the enhanced log captures the action.
When I use JSL to click on OK, the log ignores this action:
subset();
window("Subset")[Button Box(2)] << click()The same platform, the same button - and a special functionality prevents the log from logging.
Argh!
According JMP support (00156411): There is no workaround for this behavior.
Oh no!
For error messages, there is the secret Batch Interactive setting which can be used to switch between Scripting and Interactive mode. Does anyone know of a similar setting for the log - to make the log verbose ?
... or deaf?
Automation and ScriptingRe: Record Subset action via logYou can capture the Source script from the subset
Names Default To Here(1);
dt = Open("$SAMPLE_DATA/Big Class.jmp");
dt << select rows(1::2);
Subset();
Window("Subset")[Button Box(2)] << click();
subset_script = Get Data Table List()[1] << Get Script("Source");
/*
// Subset data table
// → Data Table("Subset of Big Class 2")
Data Table("Big Class") << Clear Select << Select Rows([1, 2]) <<
Subset(Selected Rows(1), Selected columns only(0));
*/
Not sure what is meant by "deaf" log, but Log Capture() can make parts of JSL to not print to log.
Re: Record Subset action via logHm, this reminds me of
TS-00035426: Update & Concatenate: source script collision
"For almost all data table manipulations, a Source script is written to the table. If one is already there, it is overwritten. This is how it has worked for many years. It is not a bug, it is intentional behavior.
If you wish to keep the code written to the Source script, it is recommended that you copy it as appropriate when it is written there. However, with the implementation of the Action Recorder, the Source script is really rendered useless. The Action Recorder is the preferred method of collecting code that JMP writes to build your own script."
