news <news@sea.gmane.org> wrote on 11/06/2006 01:14:06 PM:
> Gunnar Wagenknecht wrote:
> > I noticed a problem with 3.3M3, Subclipse 1.1.8 and a fresh workspace
> > today. Looks like some key bindings are off. I'm not confident that
it's
> > caused by Subclipse so I filled a bug with Eclipse.
>
> It turned out that the dialog appears because the file is read only. No
> I'm confused because the file is not in the repository, i.e. I just
> copied it into my project.
>
> Should I open a bug for this? I think it's wrong to show the lock file
> dialog for files that are not part of a repository but that are read
only.
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?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Nov 6 21:15:22 2006