Namespace: check the other logs

[#1]

No question, just for documentation. Perhaps somebody else faced/faces a similar problem.

If the embedded log is enabled for a script window, error messages don't show up in the "official" log window.

They are sent to the embedded log at the bottom of the script edit window. Very convenient.

I just had a strange namespace error and couldn't understand why. An error helped me to understand the problem:

A faulty code was sent to a GraphBuilder object and (after clicking on the Graph) the script stopped.
In the GraphBuilder Window, there was a message that details of the error can be found in the log:

hogi_2-1668273591805.png

But the "log" was empty. Actually: the embeded log of the fauly JSL code.

Digging deeper, I found the log message somewhere else:

The error happened in the GraphBuilder object - which was generated by the first script on the left, so the error shows up there.
.. and not in the Log window of the right window - with the faulty code.

This also solved my original problem: 

Functions in the JSL code on the right, which could not be accessed by code which was "implanted" into the Graphbuilder object (which is "at home" in code1 on the left).

Setting up a defined Namespace solved the issue:
https://community.jmp.com/t5/Discussions/Line-Profile-in-JMP/m-p/567912/highlight/true#M77887 

hogi_1-1668272885690.png

View more...

Graphbuilder code:

Names Default to Here(1);
Open( "$SAMPLE_DATA/Big Class.jmp" );
gb = Graph Builder(
	Size( 437, 413 ),
	Graph Spacing( 4 ),
	Variables( X( :height ), Y( :weight ), Overlay( :sex ) ),
	Elements( Points( X, Y, Legend( 1 ) ), Smoother( X, Y, Legend( 2 ) ) )
);
	

faulty code:

gbfb =Current Report()["Graph Builder"][FrameBox(1)];

gbfb << missingFunction_1(); // Doesn't exit

gbfb<< add graphics script(	Mousetrap(missingFunction_2())); // Doesn't exit

[#2]

This behavior can be used to access the Namespace of the GraphBuilder object - or a scripting window.
- soo helpful : )

#NamespaceInspector