ghosts when a movable panel is dragged

[wai.chan]

I have a dll application that displays a panel of outputs. For some reason, when instantiated for the first time from a C# driver, this panel leaves a trace of ghost windows on the display (much worse on XP as compared to Server 2008). This effect is repeatable everytime. When I change the setting of the panel to not-movable, then the panel is stuck whenever an event is detected (say when the Minimize button is clicked) until the mouse leaves the panel and does something to its icon in the task bar.

The way to workaround that issue is to exit the panel (which doesn't do anything except calling QuitUserInterface() followed by a DiscardPanel()) and restart it from the driver, then in the new instances everything will work as designed. That tells me that in short of exiting the window the first time, the panel appl is trapped in a state that is different than all succeeding instances.

Can anyone help?

[rcaimano]

Could you provide a screenshot or a short video of the effect you're seeing?

Do you have access to the source code of this DLL? I would be curious to see how the code is initialized when it first runs.

[wai.chan]

Thanks Riccardo. I'll try to get a screen capture and an excerpt of the code to you next week.

[wai.chan]

Ricardo, attached is the screen capture when it runs the first time from the driver (a C# app). I have also included the uir file. Please send me your email address if you'd like to see a part of the source code.

Thank you so much! Wai

[hnesmith]

Wai Chan, 

If you create a simple UI application that has only a movable panel, do you see the same behavior when you drag the image? 

[wai.chan]

Sorry for taking so far to respond...

No, if the app is run as a standalone, this doesn't happen. This only happens when I call the CVI function via a dll (that creates the panel) made with a C# GUI app. Then, as I indicated, if I call the same function again from the same C# app (same instance), everything works fine.

[rcaimano]

Just to confirm, the C# app running without CVI does not cause this issue? Have you tried creating a simple C UI in CIV without making DLL calls? Does this produce the same behavior?