Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gkerber]

Sometime back, the properties window did not save ANY changes until it was closed.  There were choices to not save any changes or to save them all.

Now ANYTIME I tab off a field in properties, or exit properties, all the changes for that field are changed.  This is bad for many reasons.

1.  What if I make a mistake?  Once I type in a field, how can I not save those changes?

2.  If the track selection is large, it's annoying to have it save that field's changes in ALL files when I plan on making more, and then wait again on the next field and so on....

I'd prefer the changes be saved when I'm done, not after every field change and some way to not-save my changes.

[nila]

Not save = Ctrl+Z - Undo

Not do them all until we've left the properties window I agree with.

It should do a general update, not per field.

[jleerigby]

I suggested some time ago that there should be an 'Apply' button within the detailed info panel.  There is a trade off though and I'm not sure it's desirable:- When changing a property and then clicking back on the library without hitting Apply would presumably discard the changes?  That would not be good.

I'm sure that Matt will have the answer.  I think what we need is for changes to be applied only in the following circumstances:

* Hit apply
* Exit or move focus away from AW

Matt - we all know how clever you are.  I bet this is a piece of ****.

[gkerber]

It used to save only after exit of properties, but now (if using docked properties) there is no real "exit" so the choice is not as clear.  But for undocked properties, apply or discard is a good choice, and one that used to be there.

For small track lists, the update after field change is noticable, but okay.  When hundreds of files are selected, it's outright annoying.  

[Doof]

How about an Apply button and a "Do you want to save changes? Yes\No\Cancel" dialog box when you click or tab out of the AW (or close it in the case of undocked)?

[Doof]

And I think you can hit escape once you've started typing in a field to discard what you've typed and go back to what was already there.

[Matt]

Version 10 may move tagging to its own thread.  That introduces other things people won't like though.

The concept of "OK / Cancel" isn't too useful once you have faith that MC can keep things synchronized.  

If we don't want an "OK" button, there's no clear time when changes should get written to the tags, so we do it right after a change now.

[jleerigby]

I see the problem and I also see Gkerbers point.  But I think if the jobs worth doing its worth doing right, not some half arsed solution, so personally I can live with it the way it is now for 9.1.  I've got used to it and can work with it.

[gkerber]

The concept of "OK / Cancel" isn't too useful once you have faith that MC can keep things synchronized.  

Not sure what you mean by this.  Sometimes I enter stuff and then don't want it.  It's lack of faith in myself that I'd like a cancel button (assuming the update didn't happen per field change).

If we don't want an "OK" button, there's no clear time when changes should get written to the tags, so we do it right after a change now.

In undocked an okay/cancel button makes perfect sense to me.  Let me change any tag field for fields, and then update when I leave properties or press okay or change the displayed record (like when I press pgup/dn).

In docked, the answers are not so clear.

[nila]

Version 10 may move tagging to its own thread.  That introduces other things people won't like though.

Not sure what this means but if it means giving us anything like a 'History' panel like we have in Photoshop then I'm all for it!