Changes and Fixed Issues in Framegrabber SDK 5.11.9#

This section provides information about changes and fixed issues for the Basler Framegrabber SDK version 5.11.9.

Updates of Components#

Updated the supported Python versions. The Framegrabber SDK now supports Python 3.9 up to Python 3.14. (Ticket ID: 343119)
Updated RapidXML from version 1.12 to version 1.13. (Ticket ID: 364973)
The pylon Event Logger, which is included in the Framegrabber SDK installation, has been updated to version 2.2.0. (Ticket ID: 364808)

Before fixing this issue, the Python wrapper handling for Fg_setParameterWithIntArray and related array setter variants could cause type conversion errors and unsafe value truncation. This has been fixed. and related array setter functions could result in type conversion errors and unintended value truncation. This has been fixed. Python sequences are now validated more thoroughly and converted to C arrays more reliably. (Ticket ID: 272185)

Before fixing this issue, cxpMagicValue was displayed as 0xffffffff in the Camera Details tab even after a successful CXP connection. The UI was not updated because the property change signal was not emitted after the value was written. This has been fixed. (Ticket ID: 368043)
Before fixing this issue, microDisplay X could crash or display images incorrectly in certain situations. This has been fixed. (Ticket ID: 365424)
Before fixing this issue, float applet parameters in microDisplay X didn't use their configured step size when changed with the editor arrow buttons. This has been fixed. (Ticket ID: 358034)
Before fixing this issue, saving images could fail when the file path contained Unicode characters, for example Chinese characters. This has been fixed. UTF-8 paths are now used throughout the SDK, and Windows file operations use Unicode-aware APIs. (Ticket ID: 363378)

Before fixing this issue, problems in the fglib board state management could cause crashes during applet operations. In some cases, memory safety issues could also occur when updating file collections. This has been fixed.(Ticket ID: 359034)
Before fixing this issue, the event queue in EventApiBridge could grow unexpectedly when an asynchronous callback returned a non-zero value. This could cause memory leaks during event handling. This has been fixed. (Ticket ID: 364916)

Before fixing this issue, applications on Windows could fail to work correctly when the user name contained non-ASCII characters. The configuration directory path was not read from the APPDATA environment variable in a Unicode-aware way. This has been fixed. On Linux, this behavior was already correct. (Ticket ID: 364407)
Before fixing this issue, loading applets from MCF configuration files could fail when applets were organized in subfolders within the board folder. In these cases, the SDK could load the first applet found in the first subfolder instead of the applet specified in the configuration. This has been fixed. The SDK now loads the applet defined in the MCF configuration. (Ticket ID: 347258)
Improved the performance of saving and loading configuration files. The required time has been reduced from about one minute to around 2 seconds. (Ticket ID: 363746)

Before fixing this issue, GenTL could generate different XML files for the same applet. The generated XML behaved correctly in GenApi, but it was not always identical. This has been fixed. (Ticket ID: 337901)

Before fixing this issue, the FPGA temperature test, DMA test, and memory test failed because the frame grabber wasn't initialized and released correctly. This has been fixed. The tests now work correctly. (Ticket ID: 364915)