-
Bug
-
Resolution: Fixed
-
P3
-
5.0
-
b37
-
sparc
-
solaris_9
Since we changed the MEmbeddedFrame in 1.5 to accept a window Id in the
constructor instead of a widget, this could cause a compatibility error.
On the one hand MEmbeddedFrame is private, but Eric tells me that we
cannot get away with the change, since this will break existing users
of MEmbeddedFrame. One way to fix this would be to check if the
value passed in is an Xt widget using (XtIsWidget) and if it is then
dont call, getWidget to create the child widget.
constructor instead of a widget, this could cause a compatibility error.
On the one hand MEmbeddedFrame is private, but Eric tells me that we
cannot get away with the change, since this will break existing users
of MEmbeddedFrame. One way to fix this would be to check if the
value passed in is an Xt widget using (XtIsWidget) and if it is then
dont call, getWidget to create the child widget.
- relates to
-
JDK-4970847 Should mention effects of 4970298 on EmbeddedFrame in release notes (AWT)
-
- Closed
-