Re: [ve-dev] fieldname change and reload

[Srimanth Gunturi <sgunturi@xxxxxxxxxx>]

Hello Janak,
        When
one renames a component (foo->bar) in the source, the update mechanism
being at a 
low level treats it as a removal of
the bean 'foo' and the addition of bean 'bar'. Now regarding a reload,
if the update mechanism found that it
was not able to merge a change into the visual (exception, failing
condition etc.) it performs a reload
from scratch. It looks like when you had the null proxy adapter for the

ULCButton, the merge mechanism didnt
think it was a failed update and happily went on without a reload -
the consequence of which was that you
didnt see a ULCButton. In the case of SWT the NPE might have 
happened at a different place/stage
such that the update mechanism knew of a problem and called the 
reload from scratch. I would be thankful
if you could provide like a stack trace of where this problem 
seems to be occuring in VE so that we
can correct it. 
Regards,
Sri.

"Janak Mulani" <janak.mulani@xxxxxxxxx>
Sent by: ve-dev-admin@xxxxxxxxxxx

11/29/2004 10:41 AM

Please respond to
ve-dev

To	"ve-Dev@Eclipse. Org" <ve-dev@xxxxxxxxxxx>
cc
Subject	[ve-dev] fieldname change and reload

Dear VE Team,

With your help and guidance we are almost ready with our release. We really
appreciate your help and thank you for the same.

However, there is one problem:

Scenario:

We have a container (ULCBoxPane) and a ULCButton in it.

If we rename the fieldname for ULCButton, VE does refresh children by
reparsing the code. However, while reparsing and adding the child
(ULCButton) to the container (ULCBoxPane), it is not able to find the
ProxyAdapter for ULCButton and neither it is able to create it
(eInternalResource() returns null because eDirectResource is null for the
button eobject and even the eInternalContainer is null).

It seems that button is removed from the model but not added back.

Could you please tell why the PA is not created during the reload after
rename of fieldname?

We need to do an explicit reload to see the button within the container
after rename. This time again, during the reload while adding the child,
it
doesnot find ProxyAdapter, however it is able to create it from the
eContainer's resource.

This behavior has been observed for both VE 1.0.1 and VE 1.0.1.1.


While debugging SWT:

I saw similar behavior, PA in primAddControl is null and there is an
exception. However, the model is built subsequently and the canvas is
repainted correctly.

What is it that is triggreing auto reload in the case of SWT? Are we missing
something?

Thanks and regards,

Janak


_______________________________________________
ve-dev mailing list
ve-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/ve-dev