Community
Participate
Working Groups
There is a problem with Wrappered (i.e. implicit came from property sheet) and Implicit visuals. The problem with Wrappered is that there is no ComponentManager assigned to it, so it fails on trying to get properties such as bounds. If we created a ComponentManager and set the beanproxy on it, then there is no clean up because the wrappered proxy host is always just thrown away with no release. The problem with implicit is that it is possible that the visual is actually shared from other properties, so we can't create a component manager for each implicit because the remote vm can only handle one manager per visual. There will be collisions. We may need to come up with a shared concept were they are registered on the remote vm for a visual. Then if the visual is disposed they can be removed. However, this won't work for awt/Swing because this is no explicit "dispose". It would also break a lot of users since we have started telling them about the manager.
