M
Matt Gilarde
Guest
I'm not familiar with the case which led to the article which recommended adding a call to ForceNativeMessageFilter but I do know something about the newer case which recommends against it. In the latter case, the call to ForceNativeMessageFilter caused an issue and we found Infragistics documentation that states that you shouldn't call ForceNativeMessageFilter if the application will also call Application.AddMessageFilter. The AVM calls Application.AddMessageFilter internally. In this case, the conflict caused a bug in the application. There may be other cases where you wouldn't see any incorrect behavior. I don't see a way to avoid the catch 22. Is this an issue for you or is it just something you noticed when reading the new article?
Continue reading...
Continue reading...