Hello Mike,
I'm using inline bindings (nothing in wod), but I tried opening either
the .html (template editor) or the .wo (wocomponent editor) with the
same content assist issue.
I'm kind of stuck in this, so I can do whatever you want to "locate"
the issue:)
Xavier
> Are you in a wod file here, or inline bindings? It's suspicious to
> me that it's going into the HTMLAssistProcessor ... Looks like it's
> probably a focus problem. I saw several 3.5-related focus issues
> when I went to record the 15 Minute Blog demo. I decided I wanted to
> figure out why they were happening before recording because it was
> pissing me off. Maybe it will end up fixing your problems.
>
> ms
>
> On Feb 10, 2010, at 10:34 AM, Xavier Destombes wrote:
>
>> Thanks for the reply Kieran:)
>> No spaces in any of my path.
>>
>> I was able to get content assist to crash, so maybe this could give
>> someone a clue. Here's the crash log:
>> !ENTRY org.eclipse.ui 4 0 2010-02-10 13:53:52.560
>> !MESSAGE assertion failed:
>> !STACK 0
>> org.eclipse.core.runtime.AssertionFailedException: assertion failed:
>> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
>> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
>> at
>> org
>> .eclipse
>> .jface
>> .text
>> .contentassist.CompletionProposal.<init>(CompletionProposal.java:72)
>> at
>> tk
>> .eclipse
>> .plugin
>> .htmleditor.assist.AssistInfo.toCompletionProposal(AssistInfo.java:
>> 57)
>> at
>> tk
>> .eclipse
>> .plugin
>> .htmleditor
>> .assist
>> .HTMLAssistProcessor
>> .computeCompletionProposals(HTMLAssistProcessor.java:291)
>> at
>> org
>> .objectstyle
>> .wolips
>> .templateeditor
>> .TemplateAssistProcessor
>> .computeCompletionProposals(TemplateAssistProcessor.java:146)
>> at
>> org
>> .eclipse
>> .jface
>> .text
>> .contentassist
>> .ContentAssistant.computeCompletionProposals(ContentAssistant.java:
>> 1832)
>> at
>> org
>> .eclipse
>> .jface
>> .text
>> .contentassist
>> .CompletionProposalPopup
>> .computeProposals(CompletionProposalPopup.java:556)
>> at
>> org.eclipse.jface.text.contentassist.CompletionProposalPopup.access
>> $16(CompletionProposalPopup.java:553)
>> at
>> org.eclipse.jface.text.contentassist.CompletionProposalPopup
>> $2.run(CompletionProposalPopup.java:488)
>> at
>> org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
>> at
>> org
>> .eclipse
>> .jface
>> .text
>> .contentassist
>> .CompletionProposalPopup.showProposals(CompletionProposalPopup.java:
>> 482)
>> at
>> org
>> .eclipse
>> .jface
>> .text
>> .contentassist
>> .ContentAssistant.showPossibleCompletions(ContentAssistant.java:1660)
>> at
>> org
>> .eclipse
>> .jface.text.source.SourceViewer.doOperation(SourceViewer.java:835)
>> at
>> org
>> .eclipse
>> .jface
>> .text
>> .source
>> .projection.ProjectionViewer.doOperation(ProjectionViewer.java:1533)
>> at org.eclipse.ui.texteditor.ContentAssistAction
>> $1.run(ContentAssistAction.java:82)
>> at
>> org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
>> at
>> org
>> .eclipse
>> .ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80)
>> at org.eclipse.jface.action.Action.runWithEvent(Action.java:
>> 498)
>> at
>> org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185)
>> at
>> org
>> .eclipse
>> .ui
>> .internal
>> .handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109)
>> at
>> org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
>> at
>> org
>> .eclipse
>> .core
>> .commands
>> .ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:
>> 508)
>> at
>> org
>> .eclipse
>> .ui
>> .internal
>> .handlers.HandlerService.executeCommand(HandlerService.java:169)
>> at
>> org
>> .eclipse
>> .ui
>> .internal
>> .keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:470)
>> at
>> org
>> .eclipse
>> .ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:824)
>> at
>> org
>> .eclipse
>> .ui
>> .internal
>> .keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880)
>> at
>> org
>> .eclipse
>> .ui
>> .internal
>> .keys
>> .WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:
>> 569)
>> at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access
>> $3(WorkbenchKeyboard.java:510)
>> at org.eclipse.ui.internal.keys.WorkbenchKeyboard
>> $KeyDownFilter.handleEvent(WorkbenchKeyboard.java:125)
>> at
>> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
>> at org.eclipse.swt.widgets.Display.filterEvent(Display.java:
>> 1131)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1597)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1622)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1607)
>> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:
>> 1659)
>> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:
>> 1654)
>> at
>> org
>> .eclipse.swt.widgets.Control.kEventUnicodeKeyPressed(Control.java:
>> 2304)
>> at
>> org
>> .eclipse
>> .swt.widgets.Composite.kEventUnicodeKeyPressed(Composite.java:605)
>> at
>> org
>> .eclipse
>> .swt.widgets.Control.kEventTextInputUnicodeForKeyEvent(Control.java:
>> 2266)
>> at
>> org
>> .eclipse
>> .swt.widgets.Canvas.kEventTextInputUnicodeForKeyEvent(Canvas.java:
>> 232)
>> at org.eclipse.swt.widgets.Widget.textInputProc(Widget.java:
>> 2054)
>> at org.eclipse.swt.widgets.Display.textInputProc(Display.java:
>> 3971)
>> at
>> org.eclipse.swt.internal.carbon.OS.SendEventToEventTarget(Native
>> Method)
>> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3051)
>> at
>> org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
>> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
>> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:
>> 2221)
>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
>> at
>> org
>> .eclipse
>> .core.databinding.observable.Realm.runWithDefault(Realm.java:332)
>> at
>> org
>> .eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:
>> 493)
>> at
>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>> at
>> org
>> .eclipse
>> .ui
>> .internal.ide.application.IDEApplication.start(IDEApplication.java:
>> 113)
>> at
>> org
>> .eclipse
>> .equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
>> at
>> org
>> .eclipse
>> .core
>> .runtime
>> .internal
>> .adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:
>> 110)
>> at
>> org
>> .eclipse
>> .core
>> .runtime
>> .internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:
>> 79)
>> at
>> org
>> .eclipse
>> .core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
>> at
>> org
>> .eclipse
>> .core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun
>> .reflect
>> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun
>> .reflect
>> .DelegatingMethodAccessorImpl
>> .invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
>> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>>
>> I'm using Eclipse Standard 3.5 Carbon with WOLips nightly 3.5
>> (latest: 3.5.6029)
>>
>> Thanks,
>>
>> Xavier
>>
>>
>>
>>> I only had that problem in Linux. I never figured it out, and I
>>> did not try too hard since it was only for work on a specific
>>> project, now long completed and deployed, that needed linux native
>>> binaries. Everything works fine for me in Snow Leopard.
>>>
>>> Sorry for not knowing the answer.
>>>
>>> One thing worth checking is to make sure there is no space in the
>>> path to your workspace *and* your eclipse executable - IIRC, that
>>> causes a few different problems, not sure if related to the one u
>>> have though.
>>>
>>>
>>> On Feb 9, 2010, at 2:09 PM, Xavier Destombes wrote:
>>>
>>>> Hello Kieran,
>>>>
>>>> I'm actually setting up a new machine and I'm experiencing the
>>>> same problem:
>>>> -code assist is OK in java file
>>>> -isn't working in a wocomponent only for the binding values
>>>>
>>>> It's under Snow Leopard with Ecplise 3.5 Carbon and latest wolips
>>>> nightly.
>>>>
>>>> How did you fix it (hopefully not reinstalling;))?
>>>>
>>>> Thanks,
>>>>
>>>> Xavier
>>>>
>>>>
>>>>
>>>>> I am currently developing a project on Linux Centos 5 using
>>>>> Eclipse 3.4.2, wolips 3.4.nightly and WO 5.3.3 (using linux
>>>>> since the project requires some commercial 3rd party native
>>>>> binaries on linux).
>>>>>
>>>>> Anyway, I cann seem to get the wod binding code assist working
>>>>> in component editor. Code assist works fine for component names
>>>>> in wod and html, but when it comes to binding names, ctrl-space
>>>>> does nothing. Anyone seen this before? Any suggestions for an
>>>>> easy fix?
>>>>>
>>>>> Regards, Kieran
>>>>>
>>>>
>>>
>>>
>>
>
>
>
This archive was generated by hypermail 2.0.0 : Wed Feb 10 2010 - 10:46:03 EST