Under certain circumstances in earlier releases, JADE notifications did not behave as expected when app.doWindowEvents was indirectly called from a .NET process.
The following applies only to .NET applications that use JADE methods exposed via the C# Exposure wizard in the JADE development environment.
If a .NET application calls exposed JADE methods and the JADE method contains a beginNotification or beginClassNotification instruction, the notification will be delivered to the thread that performed the .NET "new JoobContext()".
A beginNotification or beginClassNotification instruction in a JADE method is regarded as subscribing to a different notification than one done via RegisterNotificationHandler or UnregisterClassNotificationHandler in .NET, even if all of the parameters are equivalent. An event that is explicitly (or implicitly) caused will be delivered to all subscribers, even if that language that caused the notification did not subscribe to the notification.
When a JoobContext is Disposed, all subscriptions are cancelled.
As the JADE code is running within .NET, the JADE process will not have an idle state, so the