[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-11-06 22:52:33 CET

news <news@sea.gmane.org> wrote on 11/06/2006 04:49:04 PM:

> 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
> > 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.

I found the code to use, I was just waiting to see if you were going to
file an issue. If you do not want to, I can just commit the fix.


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Nov 6 22:52:40 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.