Opening eclipse from SL throws an error

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open a script in SL
2. Press the Edit button (after configuring the SL External Editor to be eclipse

What is the expected output? What do you see instead?
I expect to open the script in eclipse, instead get:
Could not open the editor: Invalid Input: Must be IFileEditorInput

What version of the product are you using? On what operating system?
I'm using the latest lslforge on Eclipse Helios on win 7 (64 bit)


Please provide any additional information below.
Error stack is:
org.eclipse.ui.PartInitException: Invalid Input: Must be IFileEditorInput
    at lslforge.editor.LSLMultiPageEditor.init(LSLMultiPageEditor.java:246)
    at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798)
    at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:647)
    at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
    at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
    at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289)
    at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2863)
    at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768)
    at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760)
    at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707)
    at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691)
    at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2674)
    at org.eclipse.ui.ide.IDE.openInternalEditorOnFileStore(IDE.java:1225)
    at org.eclipse.ui.internal.ide.application.DelayedEventsProcessor$1.run(DelayedEventsProcessor.java:106)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    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:369)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1384)

Original issue reported on code.google.com by Chloe198...@gmail.com on 1 Apr 2013 at 8:28

[GoogleCodeExporter]

The problem also occurs in eclipse 4.2 Classic

Original comment by Chloe198...@gmail.com on 1 Apr 2013 at 11:06

[GoogleCodeExporter]

Due to the way Eclipse requires everything to be in a project/workspace, simply 
invoking Eclipse will not work.  Will keep this issue open though - we really 
want to fix this in a future release, but unfortunately it's not a simple fix, 
so it might be a few releases before we can get to it. 

- Newfie

Original comment by elnew...@gmail.com on 9 May 2013 at 2:45

• Changed state: Accepted

[GoogleCodeExporter]

Does this mean it's impossible at this time to actually save a file in eclipse 
and have it automatically update the script in Second Life?

Original comment by Tryptofa...@gmail.com on 27 Jul 2013 at 3:36

[GoogleCodeExporter]

Sadly, that's exactly what it means. Thus, I'm reduced to cut and paste for 
getting files from eclipse into SL. I miss the convenience of being able to 
open the file in SL, press the Edit button at the bottom of the window and have 
the file duplicated in eclipse - that was an extremely convenient feature of 
lslPlus.

Original comment by Chloe198...@gmail.com on 27 Jul 2013 at 3:57

[GoogleCodeExporter]

Is there still no solution for this issue? Why am I able to open a .txt file 
with Eclipse via right-click, Open with, then select eclipse.exe ? It's a newly 
created text file in my Downloads folder and not apart of any project/workspace.

Original comment by acidicc...@gmail.com on 25 Jul 2014 at 8:41