| ID |
Description |
| 42545 |
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. |
| 48550 |
The STATUS Keyword for EXIT Does Not Work in IDL Workbench
The EXIT procedure quits the IDL Workbench and exits back to the operating system. IDL does not correctly return the exit status set by the STATUS keyword. |
48917
49373
55393 |
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, IDL will 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. |
| 49236 |
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. |
51318
51320
51322 |
Formatter Preferences for Keywords, System Variables, and Structure and Class Names are Ignored by the Source→Format Command
The keyword, system variable, and structure 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. |
| 57427 |
Internationalization: Licensing Failure
Licensing fails if IDL is installed in a location with an extended ASCII character set. |
| 58532 |
Default UTF-8 Encoding is Corrupting .pro Files with Non-English Characters
Non-English characters are converted to symbols when imported into the IDL Workbench. Importing a .pro file 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 6Text 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 encoding preference.
|
57214
58285
58839 |
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. |
| 60473 |
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. |
| 60525 |
Help May Not Display In Viewer
In rare cases, the online help may not display correctly in the IDL Help viewer. Workaround: Open a browser and navigate to IDL82\help\online_help\IDL\idl.html in your IDL installation. |
| 61842 |
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. |
| 62566 |
GRIB_OPEN Fails with "~" tilde Character in File Path
Workaround: Use fully qualified path. |
63902
52705 |
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. |
| 64864 |
On Windows and Solaris, Some OPeNDAP Functionality Does Not Work with NetCDF
Windows and Solaris users cannot take advantage of OPeNDAP functionality when using NetCDF. |