Igor Pro 7 Frequently Asked Questions

This page covers common questions about Igor Pro 7. The material below may not yet be incorporated into the help files that come with Igor Pro.

Why do characters that use Symbol font not look correct in annotations, axis labels, etc.?

Execute the following command to bring up a help topic that explains this situation in more detail:

DisplayHelpTopic "Symbol Font"

On Macintosh, why do the tool palette and graph info box fail to stay attached to a window when moving the window around? And why do these fall in the shadow of the main window? 

The technology used to implement these grouped windows in Igor Pro 6 is no longer available in Cocoa, which is Apple's current graphics API. We've done the best we can to replicate the Igor Pro 6 behavior, but unfortunately the OS simply does not provide the functionality we need to get the exact same behavior.

Why has some Data Browser behavior changed?

The Data Browser was completely rewritten, and the tree view control we are now using works differently in some respects than the Data Browser in Igor Pro 6. The item(s) below are know issues that may be addressed in the future:

  1. In order to edit multiple waves in a table, you should select them, right click, and choose Edit. Previously you could double click on the group of selected waves to edit them. It is still possible to double click a single wave to edit it in a table.

I'm using Windows with a High-DPI/4K/High Resolution display. Why do some parts of Igor, such as icons in buttons, some cursors, control panels, etc. look improperly sized?

Execute the following command to bring up a help topic that explains this situation in more detail:

DisplayHelpTopic "Windows High-DPI Recommendations"

If I save an experiment using Igor Pro 7 and open it in Igor Pro 6, the bullet characters in the history window are replaced by • (on Windows) or ‚Ä¢ (on OS X). Why is this?

This is an expected consequence of Igor Pro 7 using Unicode (UTF-8), and Igor Pro 6 using system text encoding. I'm afraid that this is something we will have to live with.

There are many other consequences of switching to UTF-8. If you're interested, execute this for the details:

DisplayHelpTopic "Text Encodings"

Why do I get unexpected results when using Igor Pro 7 with Spaces on Macintosh OS X?

Using Macintosh Spaces with Igor requires care. The common use case for Spaces and Igor is to put all Igor windows into one Space so that Igor windows can be hidden or shown all at once. That use works fine.

Problems can arise if you have Igor windows existing in different Spaces. In particular, if you have two monitors, and you have turned on the Mission Control setting "Displays have separate Spaces", you can see one possible problem with this sequence:

Make two graphs.
Drag one graph to your second monitor, which puts it into a different Space.
With that graph as the active window, pull down the Graph menu on that monitor. Select Packages->Make Traces Different.

You will see the Make Traces Different control panel appear first on your main monitor, then move to the second monitor. Appearing on the main monitor causes that Space on that monitor to become active, and the first graph becomes the active window at the same time. Now elements of the control panel appear in the graph and run-time errors occur. The control panel is a mess.

We don't have a good solution to tracking changes in window activation when we don't expect it. So our recommendations are:

  1. We don't recommend the "Displays have separate Spaces" setting.
  2. But if you're careful, you can use that setting, but you need to keep all of Igor's windows in one Space.
  3. Those with just one monitor won't have the "Displays have separate Spaces" setting, but you might still have multiple Spaces on your one monitor. The recommendation still stands: make sure Igor windows are all in one Space.

Why does Igor Pro 7 64-bit on my Windows machine crash any time a file open or file save dialog is displayed?

This is likely caused by an interaction with the Dell Backup and Recovery application. A detailed description of the problem and the solution is provided here.

Obsolete Questions

These questions are no longer relevant. If you observe the behavior described, you should update to the latest release.