Improper ComponentDispatcher.ThreadIdle with WPF studio - WPF Studio, Themes, and Shared Library for WPF Forum

Posted 16 years ago by Tim Solovyov

Version: 4.5.0485

Hi!

I've created simple WPF application and added such a code:

int _count = 0;
System.Windows.Interop.ComponentDispatcher.ThreadIdle += delegate
{
++_count;
Trace.WriteLine("ThreadIdle [" + _count + "]");
};

ThreadIdle event triggers in the expected way (e.g. it happens after mouse moved upon window and is not triggered without user activity).

However, once Actipro WPF Studio was added into the application ThreadIdle event become happened too often even without user activity (the Docking & MDI (for WPF) Support was integrated namely).

Spy++ tool shows that window is flooded by "MilChannelNotify" (0xC28D) registered windows message (several messages per second happened).

So, I have several questions:
1. Is WPF Studio really posts "MilChannelNotify" registered messages into the window?
2. Can it be due to a trial version of WPF Studio and will it be absent in licensed one?
3. If not, how to gain the proper Idle event?

Thanks.

Comments (2)

Posted 16 years ago by Actipro Software Support - Cleveland, OH, USA

Hi Tim,

Thank you for the post. We've spent a while today on this and found that yes, it indeed is the license nag screen. On full releases (after you purchase), it no longer would happen since the nag screen doesn't show there.

Narrowing down, we found that the animations on the window were not releasing the window so we added some code to fix that problem for the next maintenance release. Regardless, it won't be a problem if you own the product, based on what we found.

Actipro Software Support

Posted 16 years ago by Tim Solovyov

Thanks, for the quick answer.

The latest build of this product (v24.1.5) was released 1 month ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.