Re: [Subclipse-users] Ctrl+1 stolen in 3.3M3 by Lock File action

Mark Phippard wrote:
> On 3.2.1, after I make this fix, what I see is that the editor simply
> cannot make changes to the file because it is read only. If a project is
> unmanaged, you get a dialog letting you know the file is read-only with an
> offer to change it. Do you think we need to recreate that code, or
> possibly reuse it? Any idea where it comes from?

I have no idea where it comes from. Probably from the ui.ide plug-in. I
think in the ClearCase plug-in we just tried to make the file writable
without showing a pop up.

I'm not sure if you can reuse the popup. But I generally find that
question annoying. If I do a change to a file than most likely on
purpose. If it wasn't on purpose than I would still have to save the
editor. But I also agree that the dialog box could be a good idea. Maybe
it can have an option like "never ask again". I think there is a dialog
class for this.

Cu, Gunnar

-- 
Gunnar Wagenknecht
gunnar@wagenknecht.org
http://wagenknecht.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org