Procedure Loader

A utility to load or unload procedure files from the User Procedures or Wavemetrics Procedures folders.

Adds a "Load or Unload..." item to the File menu and, rather presumptuously, takes over the cmd-1/ctrl-1 shortcut.

Unless you are a developer, you can skip to the last section.


Click the cog icon to change advanced settings.

Fast Search: Faster to build the list of procedures, but intolerant of semicolons in file paths.

Show File Path: Hover over a procedure name to display the file location within the Igor Pro User Files folder.

Compiler Directives: Hover over a procedure name to display Pragma statements from the procedure file.

Open IM: Allow independent modules to be opened for editing when the loaded procedure is double-clicked. Other procedure windows can always be opened this way.

Obsolete WM procedures: By default these are hidden.

Drag & Drop: Drag procedures from one list to the other to load or to unload.

Hidden Procedures: Developers can hide certain procedures from the procedure loader. 'Show hidden procedures' overrides this setting, and is not recommended for normal use.

Don't Check Igor Version: enables loading of procedure files with an incompatible IgorVersion pragma.

How to hide a procedure file from the procedure loader

Insert a comment in the procedure, somewhere near the top, with the instruction 'Procedure Loader Hide'. The comment must be within 20 lines from the start of the file. This method may be revised in future versions, but for now this seems to work tolerably well.

// The following commented line hides this file from the procedure loader:
// Procedure Loader Hide

How to install

It makes sense for this procedure to be loaded at startup, so a good place to store it is in the Igor Procedures folder (see Help > Show Igor Pro User Files). If you use the IgorExchange installer to install the procedure loader it will by default be installed in the Igor Procedures folder.

Personally, I keep only one procedure file in the Igor Procedures folder: a file that has the sole purpose of including my personal selection of user procedures and Wavemetrics procedures at startup. It looks like this:


Project Details

Current Project Release

UserProcLoader IGOR.7.00.x-2.50

Release File:
Version: IGOR.7.00.x-2.50
Version Date: Tue, 02/27/2024 - 12:34 am
Version Major: 2
Version Patch Level: 5
OS Compatibility: Windows Mac-Intel
Release Notes:
fixes strconstant syntax errors
View All Releases

Thanks for publishing that. I've played around with it, it is much more useful than my hack.


I had to tweak one line in recursiveProcList()

SpecialDirPath("Igor Pro User Files",0,0,0) + "User Procedures"



It also does currently not follow windows style shortcuts to folders. The function


I'm using at… supports shortcuts but is slower as it supports semicolons in names as well.

Using that could be done with something like

string str = GetAllFilesRecursivelyFromPath("tempPathFF")
return replacestring("|", SortList(GrepList(str, ".*\.ipf$", 0, "|"), "|"), ";")

but would require that you extract it out of MIES.


EDIT: I'm on windows

Thank you, Thomas.

Good catch of the SpecialDirPath - that would lead to problems if ipf files are stored in User Files but outside of User Procedures and Igor Procedures.

And yes, the relatively simple recursiveProcList() doesn't follow shortcuts on either platform. This was originally for end users who would install packages only in the  User Procedures folder - my installer doesn't allow other options - so didn't need the complication of following links. But, since files can be #included that way, I should probably think about an update. I'll take a careful look at your GetAllFilesRecursivelyFromPath() function. I also discovered a lot of other useful utilities in your repository file! Thanks for that.

while updating this code I discovered two things that make no sense to me:

// this returns a list of filenames using a separator string that's legal in filenames on both mac and windows:
IndexedFile(path, -1, "????")

// this won't compile:
wave /T w
w = ParseFilePath(0, w, ":", 1, 0)


@tony: Thanks for the update.

Function dostuff()
    wave /T w
    w = ParseFilePath(0, w, ":", 1, 0)

does compile here on IP8.

Function dostuff()
    wave /T w
    w = ParseFilePath(0, w, ":", 1, 0)

Works in Igor 9, too. I guess this converts the paths like "C:folder:file.txt" in the text wave to just "file.txt".

That kind of code needs an explanation comment.


That exchange about the wave assignment dates back to 2019, and whatever was going on back then is long since forgotten :)

Your point about commenting abstruse code is well taken.


// this returns a list of filenames using a separator string that's legal in filenames on both mac and windows:
IndexedFile(path, -1, "????")

In Igor 8 Indexed file doesn't have an optional parameter for the separator string. Igor 8 always uses a ";" separator to separate the list. Apparently you can use that character in a file name(!).

So Igor 9 has a new optional separator parameter so you can avoid the problem. I don't think that "\r" is a valid file name character, so I'd try that. Use "????" for the optional creatorStr you'd need to specify in order to get to the last optional separatorStr parameter.




Igor Pro 9

Learn More

Igor XOP Toolkit

Learn More

Igor NIDAQ Tools MX

Learn More