Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 352988

Summary:

[OLE exception] [error behavior] If an extension is not registered in Windows Eclipse opens a read-only editor for the file instead of just opening it some other way

Product:

[Eclipse Project] Platform

Reporter:

Helmut J. Haigermoser <helmut.haigermoser>

Component:

SWT

Assignee:

Platform-SWT-Inbox <platform-swt-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

mober.at+eclipse

Version:

3.7

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

stalebug

Attachments:

Description	Flags
Exception dialog, clicking OK there will lead to the bug	none

Description Helmut J. Haigermoser

2011-07-25 06:42:14 EDT

Build Identifier: 

On windows "Open with In-Place Editor" will use editors from the system. However, if the system cannot supply an editor the response is an error dialog (see attached ping), which is fine. However, that error dialog only has an OK button, and using that Eclipse will bring up an editor area that cannot be used. The title indicates the file name, but that's it. One has to close the editor and open the file some other way. I suggest a different behavior:
- On error, close the editor area,
- On error, have a way to "Open in" with a combo box defaulting to "Text editor" or something.

Reproducible: Always

Steps to Reproduce:
1. Windows: create a project, create a file x.doesnotexist
2. Right-click on the new file, Open with -> In-Place Editor
3. See the error message, click OK\
4. Try to use the broken editor

Comment 1 Helmut J. Haigermoser

2011-07-25 06:42:50 EDT

Created attachment 200265 [details]
Exception dialog, clicking OK there will lead to the bug

Comment 2 Martin Oberhuber

2011-07-25 06:59:01 EDT

CQ:WIND00187374
Not opening an editor at all would seem more appropriate than opening an empty unusable editor frame.

Comment 3 Lars Vogel

2019-11-14 03:31:58 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.