Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Visual Editor (VE) » properties can be set but not shown after reload Visual Editor
properties can be set but not shown after reload Visual Editor [message #49817] Tue, 13 July 2004 15:57 Go to next message
Eclipse UserFriend
Originally posted by: peter.villiger.gmx.ch

Hi,



there are properties they can be set and shown correctly by property editor.
But after reopen the Visual Editor the property view doesn't show the
property value.

This happens to String property set by a constant and String[] property set
by constants.



aBean.setPropertyName(CONST_A);

aBean.setPropertyNames( new String[] {CONST_A,CONST_B} );



I this a bug which should be posted?



I use Eclipse 3.0, Visual Editor I20040706



Thanks and regards

peter



log:



!ENTRY org.eclipse.ve.java.core 2 0 Jul 13, 2004 17:45:04.522
!MESSAGE Exception thrown.
!STACK 0
java.lang.InstantiationException: IWAV0125E "new String[]{CONST_A, CONST_B}"
is too complicated to be evaluated
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanProxyFa ctory.createBean
Proxy(REMStandardBeanProxyFactory.java:262)
at
org.eclipse.jem.internal.proxy.remote.REMAbstractBeanTypePro xy.newInstance(R
EMAbstractBeanTypeProxy.java:239)
at
org.eclipse.ve.internal.java.core.BasicAllocationProcesser.i nstantiateWithSt
ring(BasicAllocationProcesser.java:210)
at
org.eclipse.ve.internal.java.core.BasicAllocationProcesser.a llocate(BasicAll
ocationProcesser.java:149)
at
org.eclipse.ve.internal.java.core.BasicAllocationProcesser.a llocate(BasicAll
ocationProcesser.java:120)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.beanProxy Allocation(BeanP
roxyAdapter.java:883)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.primInsta ntiateBeanProxy(
BeanProxyAdapter.java:832)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantia teBeanProxy(Bean
ProxyAdapter.java:762)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.applied(B eanProxyAdapter.
java:257)
at
org.eclipse.ve.internal.jfc.core.ComponentProxyAdapter.appli ed(ComponentProx
yAdapter.java:166)
at
org.eclipse.ve.internal.jfc.core.ContainerProxyAdapter.appli ed(ContainerProx
yAdapter.java:57)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.applyAllS ettings(BeanProx
yAdapter.java:544)
at
org.eclipse.ve.internal.jfc.core.ComponentProxyAdapter.apply AllSettings(Comp
onentProxyAdapter.java:635)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantia teBeanProxy(Bean
ProxyAdapter.java:764)
at
org.eclipse.ve.internal.jfc.core.ContainerProxyAdapter.addCo mponentWithConst
raint(ContainerProxyAdapter.java:221)
at
org.eclipse.ve.internal.jfc.core.ContainerProxyAdapter.addCo mponent(Containe
rProxyAdapter.java:189)
at
org.eclipse.ve.internal.jfc.core.ContainerProxyAdapter.appli ed(ContainerProx
yAdapter.java:55)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.appliedLi st(BeanProxyAdap
ter.java:184)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.applyAllS ettings(BeanProx
yAdapter.java:540)
at
org.eclipse.ve.internal.jfc.core.ComponentProxyAdapter.apply AllSettings(Comp
onentProxyAdapter.java:635)
at
org.eclipse.ve.internal.java.core.BeanProxyAdapter.instantia teBeanProxy(Bean
ProxyAdapter.java:764)
at
org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itSetting(Compos
itionProxyAdapter.java:143)
at
org.eclipse.ve.internal.java.core.CompositionProxyAdapter.in itBeanProxy(Comp
ositionProxyAdapter.java:115)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.r
un(JavaVisualEditorPart.java:1464)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

Report message to a moderator

Re: properties can be set but not shown after reload Visual Editor [message #49847 is a reply to message #49817] Tue, 13 July 2004 17:14 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.NO.SPAM.us.ibm.com

For now please fully-qualify the constants. We don't resolve
non-qualified properties yet. We are working on that and it should work
in a later driver, hopefully soon. Also the constants must be statics.
We won't be able to see non-statics.

It is possible that it may not be able to handle even fully-qualified
constants in the array. Arrays are still being worked on at this time.

Also, if the constants are in the class being edited, they won't show on
the VE until the class has been saved and compiled. That is because we
use java reflection to find them from the .class file and until then
there is no class file.


--
Thanks, Rich Kulp


Report message to a moderator

Re: properties can be set but not shown after reload Visual Editor [message #50068 is a reply to message #49817] Wed, 14 July 2004 08:25 Go to previous messageGo to next message
David Pérez is currently offline David PérezFriend
Messages: 52
Registered: July 2009
Member
suva wrote:

> I use Eclipse 3.0, Visual Editor I20040706
Why don't you use a stable build like "1.0 Stream Stable Build S20040628"?

Report message to a moderator

Re: properties can be set but not shown after reload Visual Editor [message #50551 is a reply to message #49847] Fri, 16 July 2004 14:16 Go to previous messageGo to next message
Peter Villiger is currently offline Peter VilligerFriend
Messages: 10
Registered: July 2009
Junior Member
Thanks for the answer.

Our constants are defined in interfaces which the gui classes implements.
public static final String CONST = "const value";

If a local constant is applied the property editor indicates the content
of the constant instead of the constant.
Now we hope that constants can be handeld in a later Release, hopefully in
one of the next.

Congratulations to the great work
Thanks a lot
Peter

Rich Kulp wrote:

> For now please fully-qualify the constants. We don't resolve
> non-qualified properties yet. We are working on that and it should work
> in a later driver, hopefully soon. Also the constants must be statics.
> We won't be able to see non-statics.

> It is possible that it may not be able to handle even fully-qualified
> constants in the array. Arrays are still being worked on at this time.

> Also, if the constants are in the class being edited, they won't show on
> the VE until the class has been saved and compiled. That is because we
> use java reflection to find them from the .class file and until then
> there is no class file.

Report message to a moderator

Re: properties can be set but not shown after reload Visual Editor [message #50658 is a reply to message #50068] Fri, 16 July 2004 14:29 Go to previous messageGo to next message
Peter Villiger is currently offline Peter VilligerFriend
Messages: 10
Registered: July 2009
Junior Member
I use integration builds just to see whether the latest Release can
already handle constants.

David Pérez wrote:

> suva wrote:

> > I use Eclipse 3.0, Visual Editor I20040706
> Why don't you use a stable build like "1.0 Stream Stable Build S20040628"?

Report message to a moderator

Re: properties can be set but not shown after reload Visual Editor [message #50686 is a reply to message #50551] Fri, 16 July 2004 14:33 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.NO.SPAM.us.ibm.com

In the property editor you will always see the "contents" of the
constants. We show you the final value. The fact that it came from
constant is not shown. In fact, at one time we did simply show the
string "CONST", and people didn't like it. They wanted to see the value.

If you change the value of a property in the property sheet it will
generate a new setting. It doesn't change the value of CONST. That would
not be a good thing to do because CONST may be used in other places.
If you want CONST to be changed, you need to go to code to do it.



--
Thanks, Rich Kulp


Report message to a moderator

Re: properties can be set but not shown after reload Visual Editor [message #595107 is a reply to message #49817] Tue, 13 July 2004 17:14 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.NO.SPAM.us.ibm.com

For now please fully-qualify the constants. We don't resolve
non-qualified properties yet. We are working on that and it should work
in a later driver, hopefully soon. Also the constants must be statics.
We won't be able to see non-statics.

It is possible that it may not be able to handle even fully-qualified
constants in the array. Arrays are still being worked on at this time.

Also, if the constants are in the class being edited, they won't show on
the VE until the class has been saved and compiled. That is because we
use java reflection to find them from the .class file and until then
there is no class file.


--
Thanks, Rich Kulp


Report message to a moderator

Re: properties can be set but not shown after reload Visual Editor [message #595168 is a reply to message #49817] Wed, 14 July 2004 08:25 Go to previous message
David Pérez is currently offline David PérezFriend
Messages: 52
Registered: July 2009
Member
suva wrote:

> I use Eclipse 3.0, Visual Editor I20040706
Why don't you use a stable build like "1.0 Stream Stable Build S20040628"?

Report message to a moderator

Re: properties can be set but not shown after reload Visual Editor [message #595358 is a reply to message #49847] Fri, 16 July 2004 14:16 Go to previous message
Peter Villiger is currently offline Peter VilligerFriend
Messages: 10
Registered: July 2009
Junior Member
Thanks for the answer.

Our constants are defined in interfaces which the gui classes implements.
public static final String CONST = "const value";

If a local constant is applied the property editor indicates the content
of the constant instead of the constant.
Now we hope that constants can be handeld in a later Release, hopefully in
one of the next.

Congratulations to the great work
Thanks a lot
Peter

Rich Kulp wrote:

> For now please fully-qualify the constants. We don't resolve
> non-qualified properties yet. We are working on that and it should work
> in a later driver, hopefully soon. Also the constants must be statics.
> We won't be able to see non-statics.

> It is possible that it may not be able to handle even fully-qualified
> constants in the array. Arrays are still being worked on at this time.

> Also, if the constants are in the class being edited, they won't show on
> the VE until the class has been saved and compiled. That is because we
> use java reflection to find them from the .class file and until then
> there is no class file.

Report message to a moderator

Re: properties can be set but not shown after reload Visual Editor [message #595402 is a reply to message #50068] Fri, 16 July 2004 14:29 Go to previous message
Peter Villiger is currently offline Peter VilligerFriend
Messages: 10
Registered: July 2009
Junior Member
I use integration builds just to see whether the latest Release can
already handle constants.

David Pérez wrote:

> suva wrote:

> > I use Eclipse 3.0, Visual Editor I20040706
> Why don't you use a stable build like "1.0 Stream Stable Build S20040628"?

Report message to a moderator

Re: properties can be set but not shown after reload Visual Editor [message #595413 is a reply to message #50551] Fri, 16 July 2004 14:33 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.NO.SPAM.us.ibm.com

In the property editor you will always see the "contents" of the
constants. We show you the final value. The fact that it came from
constant is not shown. In fact, at one time we did simply show the
string "CONST", and people didn't like it. They wanted to see the value.

If you change the value of a property in the property sheet it will
generate a new setting. It doesn't change the value of CONST. That would
not be a good thing to do because CONST may be used in other places.
If you want CONST to be changed, you need to go to code to do it.



--
Thanks, Rich Kulp


Report message to a moderator

Previous Topic:Nice to have getJLabel()
Next Topic:SWT controls
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Wed Jul 17 14:30:36 GMT 2024

Powered by FUDForum. Page generated in 0.03826 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly