"Martin Letenay" <email@example.com> wrote on 09/29/2005 08:25:34 AM:
> I think I'm starting to dislike the current behavior of dirty decorators
> When deep-cheking of folders is turned on, they are marked dirty
> of its children is dirty.
> And as dirty are also considered unversioned files.
> What about a small modification:
> - when "select unversioned resources on commit" preference is set ON,
> behavior will be unchanged.
> - when "select unversioned resources on commit" preference is set OFF,
> those unversioned resources
> will be ignored and the parent folder will NOT be marked as dirty ?
I have never seen the existence of an unversioned file cause the decorator
to come on. Ever. If you are seeing that, I bet it is part of your
recent changes. Are you proposing to add that behavior? If so, then I
think conditioning it the way you have proposed would be appropriate.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
Received on Thu Sep 29 23:01:39 2005