CXTPObservable leaks during XTPShutdown

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi, I am currently migrating from CodeJock 19.3 to CodeJock 24.0 and found that this issue is occurring to me. I use the static function CXTPPaintManager::SetTheme(xtpThemeVisualStudio2015) to set the theme for the paint manager. 
However, when I call CXTPWinApp::ExitInstance(), and as the app starts to close, when XTPShutdown() is called during ~XTPApplication(), I get an assertion error during:
template<class Owner, class Observer>
AFX_INLINE CXTPObservable<Owner, Observer>::~CXTPObservable()
{
    ASSERT("All observers must be unsubscribed before destruction" && 0 == m_Observers.GetSize());
}

I can use CXTPPaintManager::SetTheme(xtpThemeOffice2000) before calling CXTPWinApp::ExitInstance(), this error doesn't occur. I wanted to ask if there is a more elegant solution, or if this workaround is the only solution at the moment.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
ganzeiss Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 25 November 2024 Status: Offline Points: 5	Post Options Post Reply Quote ganzeiss Report Post Thanks(0) Quote Reply Topic: CXTPObservable leaks during XTPShutdown Posted: 20 hours 10 minutes ago at 9:19pm
	Hi, I am currently migrating from CodeJock 19.3 to CodeJock 24.0 and found that this issue is occurring to me. I use the static function CXTPPaintManager::SetTheme(xtpThemeVisualStudio2015) to set the theme for the paint manager. However, when I call CXTPWinApp::ExitInstance(), and as the app starts to close, when XTPShutdown() is called during ~XTPApplication(), I get an assertion error during: template<class Owner, class Observer> AFX_INLINE CXTPObservable<Owner, Observer>::~CXTPObservable() { ASSERT("All observers must be unsubscribed before destruction" && 0 == m_Observers.GetSize()); } I can use CXTPPaintManager::SetTheme(xtpThemeOffice2000) before calling CXTPWinApp::ExitInstance(), this error doesn't occur. I wanted to ask if there is a more elegant solution, or if this workaround is the only solution at the moment.