Refresh Screen when returning to a Modal Popup

As a followup - the problem seems to be refreshing the RibbonBar is causing the problem - I remarked out all the ribbonbar code and the program works correctly.  is there any kind of refresh setting on the ribbonbar that I should set on/off that would cause this.   Basically, when another program gets the focus and is in front of my program, when I use the startbar icon to get focus back on my program it seems to go through some kind of screen refresh that locks  my program when the ribbonbar is repainting.  any insight would be greatly appreciated.

Hi,

I have also been battliing this issue now for a couple of days.  It didn't work in 13.3 and its still not fixed in 13.4.2.  (This is an extreamly large project which we (5 team members) have spent the last 8 weeks converting to use codejock (all our screens need tweeking in some manner).

I tied the issue down to
- Have a non modal mdi child window open
- Open another non modal mdi child window
- Click on a button that opens a modal window (some times you need to go two modal windows deep)
- Change focus to an application that covers it up
- Switch focus back
- Its now hung, the windows white out and the processor is between 90% and 100%

I then removed controls off the forms to discover if it was the modal or non modal windows that were causing the issue.  I the end I tied to down to the first non modal form I opened having a "SSActiveToolbars" control on it.  This is an old active X control from Infragistics.

If i remove this control then it all works fine.  I then also tied the issue down to the same line that you have. 

I then created a test app to verify this issue.  The first non modal form only needs the control on (no code, setup, visible=false, enabled=false, etc) to cause the crash.

I have tried using "RemoveWindowClass" and "ExcludeModule" but they don't seem to have any effect.  Note I have used the spy++ and did add the classes found to the RemoveWindowClass routine.

I have also tried to use the .RemoveWindow routine but the control does not provide a hwnd.  I used a couple of API calls to get this but it seemed to have no effect.  I am not 100% sure it was getting me the correct hwnd as the toolbar does not seem to appear as a window in spy++ (only SSTracker) is shown?


I have uploaded my example code
uploads/6296/CodeJockMDIissue_-_with_remove.zip

Does anyone have any advice?

I cannot replace the toolbar with the codejock toolbar as we have over 300 in our system and we are already cutting it fine.

Hi,

Thanks for looking at this.  The DLL needs registering.  It also needs Msvcrt.dll.

Are you running the exe or opening the project?  The control is licensed and i'm not sure if I can pass the license out.

I could knock up an installer if the DLL register fails.

Thanks again!

I"m sorry I just double checked and the form that I thought was not using ActiveToolBars actually is...  so strike that - that may be the problem causer, but like you I can't replace it easily...

Hemesh! Can you share the skin that you present us?
Thx

YES!!! CONFIRMED LOCK  - Exactly the same results as in my software.    had to change a few items around due to CodeJock version I'm running but when all was said and done it did the exact same problem.   Now, the question will be... will they just blame it on ACTIVE TOOL BAR and not do anything...

Any word on this?

I've also just added a note to my case mentioning your interest again

Hi,

Good news!  CJ have fixed the issue and given me a test 13.4.2 DLL to check it out!  It seems to work! I've attached it if you want to test it too.

uploads/6296/Codejock.CommandBars.v13.4.2.zip

This will be in the 15 Beta out mid Jan!

Oleg has very kindly offered to create me a "signed isolated version based on 13.4.2" as we cannot wait for the 15 beta out mid Jan.
(but we also have a crystal reports scrollbar issue too so I’m trying to get that squeezed in too).

I'm very impressed that Oleg has fixed this issue!  We've invested a lot of time converting our product and were a little apprehensive that we had found a potential show stopper.  (It looked like a very very tricky little bug to track down and fix.)

Theres no code changes needed.

I replaced the standard 13.4.2 dll with the attached test one and the lockup issue has now gone

Hemesh,  can you ask Oleg if he can make the same change for V13.2.1?