nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

run table script

hogi

What is the difference between running a Table Script via the green Play icon:

... and via the Run button?

Accepted answers

All comments

jthi

Is there are reason to suspect that there is a difference? From the script "window" you can for example run separate parts by highlighting them.

Byron_JMP

They generally do the same thing.

The little green arrow is faster, one click.

: )

hogi

After inventing the 3rd "solutions" to a "timing issue" in a table script - unfortunately without real success

... I found out that the actual difference was:

run the script via the play icon → issue
open the script window - [try some new code ... or nothing] - and click on the Run button → no issue.

hogi

I thought so too ...

txnelson

Running by clicking on the Green Run Arrow, runs the script on the data table it is attached to.

Running the script from the Edit window, runs the script on the Currently Active Data Table, which may not be the data table the script was saved to.

hogi

Good idea,
but actually, for "Edit" mode I paid attention to have "my table" active before clicking on run.

And: it is the "Edit" mode which works

:)maybe it's related to a current data table() somewhere in the code - which might act differently if the script is started via the play icon - or via the Run button.

:)just putting a :)current data table() directly into a table script did not show a difference between the two approaches.

But my code is a lengthy chain of JSL, Main Menu (" ... "), open file, join, concatenate ...

:)I will try to reduce the complexity to show the difference - or to generate an anonymized example ...