|IDLffVideoWrite Cannot Create Animated GIFs
Because of vendor issues in the ffmpeg library, IDLffVideoWrite cannot create animated GIF files. Use the WRITE_GIF routine instead.
|Installation error on Windows platforms: "Key not valid for use in specified state"
Some customers have reported this error during the installation process. It is caused by a Microsoft update (KB2918614), which affects the Windows installer service. Workaround:uninstall this Microsoft update. For more information, see the Microsoft Community website.
||WIDGET_TREE Drop Event Can Cause IDL to Crash if an Error Exists in the DRAG_NOTIFY Callback Routine
If there is an error (such as an undefined variable) in the custom DRAG_NOTIFY callback routine, IDL may freeze or crash since the error halts execution in the child routine and IDL cannot return to the calling function.
Workaround: Handle potential problems in the callback routine by including CATCH statements in your code. See the documentation topic "Responding to Drag Notifications (Callbacks)" for more information.
||Breakpoints in Files Opened via Links, Shortcuts, or Alternate Paths
To improve performance, IDL always compiles the first version of a file it finds in its path. If you open a file in the editor and set a breakpoint, then compile from a version of the same file with a different path, IDLwill not assume that the two files are the same. As a result, IDL will not stop at the breakpoint set in the second file. Alternate paths to the same file can be constructed via UNIX links, Windows shortcuts, mapped drives, or UNC paths.
Workaround: Make sure that the full path to the file in which you set the breakpoint is the same as the full path to the compiled file. If you use the IDL Workbench, compiling using the Workbench menus or toolbars will ensure that the same path is used for compilation and debugging.
||Deleting a Project or a Directory Within a Project While the Project Is Open Causes Exceptions when the Workbench Exits
When a project file or a directory within a project is deleted from outside the Workbench (for example, from Windows Project Explorer) while the project is open, a warning message may be issued while the Workbench is still running. An exception may occur on exiting the Workbench.
|Formatter Preferences for Keywords and Class Names are Ignored by the Source > Format Command
The keyword and class name formatting preferences set on the IDL Formatter preference page are not applied when the code is highlighted and the Source > Format command is selected.
||Default UTF-8 Encoding is Corrupting .pro Files with Non-English Characters
Non-English characters are converted to symbols when imported into the IDLWorkbench. Importing a .profile containing non-English characters in IDL permanently corrupts the file with bad characters. Workaround: Before opening a file or before saving an open file, change the file encoding to ISO-8859-1 for Spanish or German, or to Shift-JIS for Japanese.
To change the encoding for an individual file, open the file in an IDL editor, then select File> Properties. In the Resources dialog box, change the Text file encoding preference.
To change the default encoding preference for IDL, select Window > Preferences. In the Preferences dialog box, choose General > Workspace. Change the Text file encodingpreference.
|IDL Crashes on Macintosh and UNIX When Performing Graphics Operations Where GL Drivers are Present
Possible workaround: Rename the gl_driver.so file (located in bin\bin.<platform>) to gl_driver.ba.
||Accessing Preferences while IDL is Busy May Hang Workbench
Trying to change Preferences while IDL is busy (for example, when a lengthy command is being executed) may cause the Workbench to hang.
||IDL on Windows 7 May Have Unpredictable Behavior When Using Graphics
The cause may be graphics cards that are unsupported in Windows 7. Please see a list of supported graphics cards on the Microsoft.com website. You may want to upgrade your graphic driver or switch the IDL Graphics preference to use software rendering.
|Using the IDL_Java Bridge Causes the Workbench to Ignore the Current Directory in CLASSPATH
Workaround: Copy the .class file to any other directory explicitly listed in CLASSPATH.