C++ samples compilation fails with a long directory name on Windows
If you are using a directory with a long name for the LuciadCPillar sample project, the build may fail. To resolve this problem, either use a shorter path, or see the Visual Studio documentation for a solution.
The performance of the C# samples is bad
The UI Debugging Tools for XAML can affect the performance of the samples in Visual Studio.
To disable these tools in Visual Studio 2019 versions older than 16.8, go to
Tools | Options | Debugging, and de-select the Enable UI Debugging Tools for XAML checkbox.
To disable these tools from Visual Studio 2019 version 16.8 onward, go to Tools | Options | Debugging | Hot Reload, and de-select the Enable XAML Hot Reload checkbox.
To disable these tools from Visual Studio 2022, to Tools | Options | Debugging | XAML Hot Reload,
and de-select the Enable XAML Hot Reload checkbox.
The application crashes before the main method is entered
Many parts of the API can only be used after the LuciadCPillar EnvironmentLuciadCPillar EnvironmentLuciadCPillar Environment
has been created. For example, this is the case for:
If you use these classes too soon, they will throw an exception. When you are using C++ for example, this can happen when you are creatingcreatingcreating a coordinate reference during static initialization.
This tutorial shows you how to create the EnvironmentEnvironmentEnvironment.
Investigate crashes
It is possible that you trigger a bug in LuciadCPillar that causes the application to crash. When this happens, LuciadCPillar tries to provide as much information as possible to allow finding the root cause of the crash.
-
It can throw an
ExceptionExceptionException. This is an exception type that contains a stack trace, next to the exception message. Note that the stack trace is not available in Release mode. -
In case of a segmentation fault, or an other fatal issue, LuciadCPillar tries to log an error to the
ILoggingBackendILoggingBackendILoggingBackend, with anExceptionExceptionExceptionthat contains a stack trace. Note that the stack trace is not available in Release mode.
Drag and Drop is not working on Windows
This is a consequence how privileges work on Windows. It happens when the application is run under admin privilege while Windows Explorer is used under normal user privileges. Lower-privileged processes cannot drag-and-drop to higher-privileged ones. This can be resolved by running the application (or Visual Studio) without admin privileges.