Forum

Dear Support,

Any news when 2.84 will be released?

Thanks,

Ron.

First of all, this problem is well known as principally never fixed issue of Windows XP and later versions:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=354617

It appeared many years ago with release of Windows XP and still not fixed. Probably, it’s easier to code new OS than fix this problem. The fixes like the following one are incorrect:

http://www.codeproject.com/KB/bugs/MDIFlick.aspx

Now the good news. It looks like we fixed it. Here is the ZIP file with compiled sample MDI applications:

http://www.prof-uis.com/download/forums/tmp/MdiFlickerFreeTests284.zip

The problem appeared when you are activating MDI child frames via menu because the CMDIFrameWnd::OnCommand() virtual method handles these menu commands in a special way when Prof-UIS expects to intercept classic WM_MDIACTIVATE messages. Now Prof-UIS also handles the MDI window menu commands in the overriden OnCommand() virtual method of the code>CExtNCW < CMDIFrameWnd ></code> specialized template class.

It also looks like all the other known problems with skinned MDI child frame windows are gone because Prof-UIS 2.84 implements most of the MDI interface features manually (window tiling and cascading for instance). We had no chance to avoid this.

Does it fix the bug in view swithcing in MDI I reported?

http://www.prof-uis.com/prof-uis/tech-support/support-forum/any-progress-with-this-bug-where-you-able-to-reproduce-it-62608.aspx#@lt;/p>

This is very important to us that this bug is fixed for swithcing to 2.84

Thanks,

Ron.

It is scheduled for December 15. We are sorry for the delay.

Does it fix the bug in view swithcing in MDI I reported?

http://www.prof-uis.com/prof-uis/tech-support/support-forum/any-progress-with-this-bug-where-you-able-to-reproduce-it-62608.aspx#@lt;/p>

This is very important to us that this bug is fixed for swithcing to 2.84

Thanks,

Ron.

First of all, this problem is well known as principally never fixed issue of Windows XP and later versions:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=354617

It appeared many years ago with release of Windows XP and still not fixed. Probably, it’s easier to code new OS than fix this problem. The fixes like the following one are incorrect:

http://www.codeproject.com/KB/bugs/MDIFlick.aspx

Now the good news. It looks like we fixed it. Here is the ZIP file with compiled sample MDI applications:

http://www.prof-uis.com/download/forums/tmp/MdiFlickerFreeTests284.zip

The problem appeared when you are activating MDI child frames via menu because the CMDIFrameWnd::OnCommand() virtual method handles these menu commands in a special way when Prof-UIS expects to intercept classic WM_MDIACTIVATE messages. Now Prof-UIS also handles the MDI window menu commands in the overriden OnCommand() virtual method of the code>CExtNCW < CMDIFrameWnd ></code> specialized template class.

It also looks like all the other known problems with skinned MDI child frame windows are gone because Prof-UIS 2.84 implements most of the MDI interface features manually (window tiling and cascading for instance). We had no chance to avoid this.

Great news... looking forward to try it on our products next week... (we are still expecting the version to be out on the 15th - right?)