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; } } }

JMP 15: Log is empty when using Projects

ionatx

I am trying to fix a script that broke following the upgrade to JMP 15, however the log is also jacked. When executing scripts from within Project windows, nothing is recorded. The scripts *are* executing, just not being written to the log.

Suggestions?

Accepted answers

jules

Hi @ionatx,

Yes, I believe to resolve ambiguity as to where log output ends up, the project log behavior changed between 14 and 15. In JMP 14, messages write to the global log unless the project log window (or an embedded log window for the script) is open in the project. In JMP 15, output always writes to the project-specific log, whether it is visible or not.

I can certainly see the value of having a free-floating log in the context of using a project, especially with a multiple monitor setup as you describe. Unfortunately, I am not aware of a way to detach the project log from the project itself, and I do not believe there is a preference for reverting to the JMP 14 behavior of writing project output to the global log when the project log is hidden. Perhaps others can suggest a workaround here, but I suggest posting your request the JMP Wish List.

@jules

All comments

jules

Hi @ionatx,

That sounds like strange behavior! Are you looking at the Log that's internal to your Project, or the global Log? When running inside of a project, script messages/output/errors only appear in the log that's a part of the project. If you don't have that log visible, go to the Project Menu > Show Log. If, on the other hand, you have the project Log panel visible but none of the expected output is writing to it, something else must be going on. I would try something simple in a new script window, such as Write(1); , and see if that returns anything to the project log. That might give us some indication as to whether there is something wrong with the project log itself, or that something is preventing your scripts from returning their error messages to the project log.

@jules

ionatx

Interesting. @jules is this project-specific log new in JMP15, or has the behavior of Ctrl+Shift+L changed? The project log does indeed work, however in the past I have always used Ctrl+Shift+L. Having a free-floating log window visible on a separate monitor is more efficient, are there settings that control these behaviors that I am failing to see?

jules

Hi @ionatx,

@jules

ionatx

Awesome, thanks @jules!