Community
Participate
Working Groups
Build Identifier: M20100909-0809 Under Windows 7 when I double-click on a bitmap file, the file will be opened in in-place editor and externaly in mspaint. If the file was changed in external editor, the in-place editor is marked as dirty. If you save the changes in the external editor, the dirty-mark in the in-place editor is removed. If you then close the external editor, the in-place editor again shows the dirty-mark. If you then try to save the changes in the in-place editor with eclipse, there is no effect at all. If you again try to save the file you get a message box: Title: Error Saving, Text: Could not save "filename" Reproducible: Always Steps to Reproduce: 1.Place a *.bmp file in the project 2. Double-click to open the file 3. Change something in the external editor (mspaint) 4. Save changes in mspaint 5. Close mspaint 6. Push save button in eclipse 7. Push save button again
I tested Eclipse 3.7.2, 3.8.2 and 4.5.1 on Windows XP and Windows 7 and it turns out that this problem depends on the MS Paint version that is used rather than the Eclipse version. On Windows XP the in-place editor action opens MS Paint within the Eclipse window but on Windows 7 the in-place editor action opens the file in the external MS Paint editor and also within the Eclipse window. I tried also MS Word 2007 on Windows 7 to check if this behavior is Windows-specific rather than Paint-specific but it behaves normally, i.e. a DOC file is opened within Eclipse window as in case of Windows XP. This seems to indicate there was a change in MS Paint embedded in Windows 7 which makes it work in a different way. I am not sure if this is an expected behavior but it definitely looks strange. Niraj, is this something you could take a look at?
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
