Professional UI Solutions
Site Map   /  Register
 
 

Forum

Please Log In to post a new message or reply to an existing one. If you are not registered, please register.

NOTE: Some forums may be read-only if you are not currently subscribed to our technical support services.

Forums » Prof-UIS Tech Support » Tile & Cascade problems with 2.83 with child templated CExtNCW Collapse All
Subject Author Date
Offer Har Aug 25, 2008 - 7:11 AM

Hi,


We’ve been trying to apply this style to out MDI application with no success.


After setting this template to the child frame, Tile and Cascade stop to function correctly.

We created a simple MDI application using MFC wizard, and added the templates to main frame and child frame - that’s all we did...


The regenerate the bug, all you have to do is this:


1) Run the application

2) Maximize the child frame opened

3) Create a second child frame (using the File->New)

4) Try tile & cascade.


If you remove the template from the child frame, it all works fine.


I will e-mail you the test project, which is basicaly a defulat MFC MDI application with Prof-UIS added to it.


Please try and fix this for version 2.84


Thanks,

Ron.


This is how it looks:


Good tile and cascade:




Bad tile & cascade, when child frame is using CExtNCW



Technical Support Sep 9, 2008 - 2:15 PM

This source code update can be used for patching 2.83. You should simply overwrite both .../Prof-UIS/Include/ExtNcFrame.h and .../Prof-UIS/Src/ExtNcFrame.cpp files when unpacking ZIP file, rebuild required Prof-UIS 2.83 library configurations and your project(s).

Offer Har Sep 9, 2008 - 3:08 PM

Thanks - will try it out.

Offer Har Sep 4, 2008 - 12:19 PM

Are you going to fix this bug?


I even sent you a saple application to reproduce it, and you don’t even bother telling me if you were able to reproduce it.


Please do so ASAP!

Technical Support Sep 6, 2008 - 9:01 AM

It is fixed. Please download the update.

ExtNcFrame-updated-files-284-Version-2.zip

Offer Har Sep 9, 2008 - 9:31 AM

I’m still using 2.83.... will wait for official 2.84 version release, or can you make this fix available for 2.83?