Indeed the issue with annotations is fixed !!!
Thanks for the effort.
Was this a general issue or was it specific for the Gupta environment?
When the last is the case, more detailed info on why there were issues with GdPicture and SqlWindows can help to improve the Gupta environment to be more compatible.
If you want you could send me a private message indicating what was the difference between say C++/VB6 using COM interface compared to SqlWindows concerning the handling of COM. This info, I could pass on to the Gupta developers to see if they can be more in line with those development environments.
Sorry for the delay.
The solution is quite hard to explain. Basically to fix the issue we've hooked the Windows messaging system in order to deliver only expected messages from your environment. Since we did not know the source code of gupta we had to trace the communication between the gupgta COM container and the GdPicture usercontrol and filtered the message that caused the crash. I think the fix is quite clean and should prevent similar issue in future released of Gupta.
Hope this clarify.
With best regards,
I'm encountering issues now which might be related to the one which was fixed earlier.
(the annotation editor issue)
It seems that when closing a form on which the viewer and/or the thumbnail components are placed, the application gets unstable when
the form is closed.
It is not immediately visible, but after opening and closing forms containing the viewer/thumbs these issues can occur:
- The viewer component does not show any images, the canvas color is the same as the form color
- The environment crashes without any message
- A .NET error pops up, like this:
Code: Select all
************** Exception Text ************** System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at System.Windows.Forms.UnsafeNativeMethods.IOleInPlaceFrame.SetActiveObject(IOleInPlaceActiveObject pActiveObject, String pszObjName) at System.Windows.Forms.Control.ActiveXImpl.InPlaceActivate(Int32 verb) at System.Windows.Forms.Control.ActiveXImpl.OnFocus(Boolean focus) at System.Windows.Forms.Control.OnGotFocus(EventArgs e) at System.Windows.Forms.Control.WmSetFocus(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WmSetFocus(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.UserControl.WmSetFocus(Message& m) at System.Windows.Forms.UserControl.WndProc(Message& m) at GdPicture10.GdViewer.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ActiveXImpl.System.Windows.Forms.IWindowTarget.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
The application creates a start-form with a button to start multiple viewer forms.
The viewer form only contains the GdViewer and the thumbnail component.
No actions are performed, only create the form and no methods or properties are set.
In all cases, every form (4 instances are created) is ok. The viewer has a black background.
Now close manually all viewer forms and press the button again to create the 4 forms.
In some cases a crash, in some only the viewer object is not black (so not working) or a .NET error pops up.
So i guess it seems related to the Annotation Editor issue. The environment combination does not clean up the instances and therefore makes it unstable.
Here is the source, you can open it in the demo version for Team Developer 6.1
I hope the issue can be found. Right now this is blocking as our application will open multiple viewers (and close them).
I'm using the latest 10.0.13 version.
I also tested with only the viewer object and only the thumbnail object.
The testcase has issues on those tests. So it seems they both separately and combined are the cause.
problem fixed for the next minor release that will be published within four days.
With best regards,
Many thanks for this quick and efficient support !
Please let me know soon if you encounter any other issue, my Gupta eval expires within 5 days
Who is online
Users browsing this forum: Baidu [Spider] and 1 guest