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

843920_en-US

liliconcom

Automatic registration of addin: support for .jmpaddin?

According to the JMP 18 help you can install one or multiple add-ins by copying the add-ins into one of two folders.

However, apparently, this only works for extracted addin folders, not for .jmpaddin files - JMP simply ignores .jmpaddin files that reside in these folders.

Is there a simple way to force JMP to install a .jmpaddin file without using the JMP GUI? Or is the only way to extract my .jmpaddin file and copy the folder to %ALLUSERSPROFILE%\JMP\JMP\AddIns resp. %APPDATA%\JMP\JMP\AddIns ?

(in case you're wondering why I need that: I'm building an InnoSetup-based installer for one of our addins that installs an ODBC driver, sets up an ODBC DSN and registers a JMP Addin that uses this ODBC DSN; the only part that is missing is the automatic registration of the JMP Addin)

Automation and Scripting

Windows

Re: Automatic registration of addin: support for .jmpaddin?

What type of solution are you looking for? Extract is one option or you could run JMP with JSL which would then take care of the installation (and exiting JMP).

Re: Automatic registration of addin: support for .jmpaddin?

Ideally, it would be something as simple as

copy myaddin.jmpaddin %APPDATA%\JMP\JMP\AddIns

and JMP would prompt on the next program start for installation of the addin.

Regarding "running JMP with JSL": I tried installing the addin with

start myaddin.jmpaddin

This launches JMP and prompts for addin installation (so far, so good). But the start command immediately returns and doesn't wait until the installation is completed, so my installer has no way of knowing whether the installation was successful or canceled by the user.

Re: Automatic registration of addin: support for .jmpaddin?

Is there any reason why user would have to do anything? With JSL you can use

Batch Interactive(1);
Try(addin_path);
Batch Interactive(0);

and it shouldn't prompt for the user. To see if add-in was installed successfully either check if folder was added or maybe utilize JSL

Get Addin(addinid)

Re: Automatic registration of addin: support for .jmpaddin?

For the time being, we're using the "copy the whole folder to %APPDATA%\JMP\JMP\AddIns" approach. It's not perfect, but it works for our purposes - thanks for all the suggestions.