Eclipse Community Forums: Visual Editor (VE) » Problems with DesignView, no rendering

Help

Home

Home » Archived » Visual Editor (VE) » Problems with DesignView, no rendering

Show: Today's Messages :: Show Polls :: Message Navigator

Problems with DesignView, no rendering [message #88167]

Fri, 22 April 2005 08:13

Maja Ostrowski

Messages: 12
Registered: July 2009

Junior Member

I just started using Eclipse and the VE and have the following problem
while trying to create a GUI:
I can see and addit the source but the graphical DesignView
stays (or gets) blank. A Loading bar appears but no rendering happens.
I use Eclipse Version 3.0.2 and VE Version 1.0.1.1.
What am I doing wrong?

I attached my logfile:

eclipse.buildId=M200409161125
java.version=1.4.1_02
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE

!ENTRY org.eclipse.ve.java.core 4 0 Apr 22, 2005 09:29:08.967
!MESSAGE Exception thrown.
!STACK 0
java.lang.ClassCastException
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.createJavaInstances(JavaSourceTranslator.java:705)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.buildCompositionModel(JavaSourceTranslator.java:774)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.decodeDocument(JavaSourceTranslator.java:881)
at
org.eclipse.ve.internal.java.codegen.core.JavaSourceTranslat or.loadModel(JavaSourceTranslator.java:656)
at
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart$Setup.run(JavaVisualEditorPart.java:1444)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

!ENTRY org.eclipse.ve.java.core 4 0 Apr 22, 2005 09:30:26.107
!MESSAGE Can not determine equivalency

Report message to a moderator

Re: Problems with DesignView, no rendering [message #88232 is a reply to message #88167]

Fri, 22 April 2005 14:03

Eclipse User

Originally posted by: richkulp.us.NO_SPAM.ibm.com

Please step up to VE 1.0.2.1. It looks like you have EMF Examples
installed, and that conflicted with the VE in 1.0.1.1. We've fixed it by
1.0.2.1.

--
Thanks,
Rich Kulp

Report message to a moderator