Via File/Preferences, you can change the standard settings of Jmp.
Very cool to adjust Jmp to your needs
But I found a subtle issue - in combination with the functionality to automatically generate JSL code (save to script, advanced log, Dashboards, log, Workflow Builder ...)
The below code changes the preferences, so - please think twice if you want to try it .
The story:
A user adjusts some settings via File/Preferences - an then generates a report with the default setting:
Names Default to Here(1);
dt = Open( "$SAMPLE_DATA/Big Class.jmp" );
Set Preferences(
Data Filter Conditional( 1 ),
Column Switcher Retain Axis Setting( 1 )
);
Graph Builder(
Variables( X( :height ), Y( :weight ), Overlay( :sex ) ),
Elements( Points( X, Y, Legend( 1 ) ), Smoother( X, Y, Legend( 2 ) ) ),
Local Data Filter(
Conditional(0),
Add Filter(
columns( :sex, :name )
)
),
Column Switcher( :weight, {:age, :weight},Retain Axis Settings( 0 ) )
)
Then he optimized the Report via the GUI and saves the script. This Script will look like the below one
(for sake of clarity: neglecting the "optimization" step):
Graph Builder(
Variables( X( :height ), Y( :weight ), Overlay( :sex ) ),
Elements( Points( X, Y, Legend( 1 ) ), Smoother( X, Y, Legend( 2 ) ) ),
Local Data Filter(
Add Filter(
columns( :sex, :name ),
Display( :name, N Items( 15 ), Find( Set Text( "" ) ) )
)
),
Column Switcher( :weight, {:age, :weight} )
)
i.e.: all default settings are automatically removed from the code - as they won't have an effect for a standard system.
Same happens if the uses uses the Report inside a Dashboard (!) - all default settings won't be added.
Now, the user runs the code again - imagine how the Report will look like ...
I can understand why it is like this - it is no bug it's a cool Feature that Jmp automatically cleans code to remove unnecessary lines.
But in combination with a user who dares to change settings in the preferences it acts like a bug.
My current workaround: Just change preferences where you are sure that you won't use the default setting.
This is great for 100 - 0% ... 50 - 50% and the special case: 0 - 100% (future usage of: % default - %different setting).
But hurts for the range above 20 - 100%
... and hurts especially for something like 99 - 1%.
Is there a better solution - how do YOU solve this issue in daily work life?