Track.Hidden and Track.Locked flags - what do they do?

dust wrote on 11/30/2003, 3:02 AM
In the script API I can see that the Track class has a "Hidden" and a "Locked" public property of type Boolean. Actually I was looking for a way to prevent changes in a whole track (instead of only lock events).

By trying these features I found that setting the "Locked" flag on didn't seem to have any influence: I could still move events around on the track. So I'm wondering what it is actually doing? Setting the "Hidden" feature actually makes the track disappear from the GUI, as expected, but as there's no GUI-support for this feature, I can't make it visible again (except maybe from within scripts). Is this an "official" behaviour, or are these flags just there as leftovers/future plans?

Thanks, dust

Comments

SonyPJM wrote on 12/1/2003, 6:56 AM
Leftovers that slipped through... expect them to go away in the next release.
dust wrote on 12/5/2003, 10:49 AM
I see... too bad, I'd like the Hidden flag to be kept, maybe even extended. I consider is as being useful for storing/backing up events. For example, a "snapshot/backup" script could put copies of all events of a project into a hidden track, so certain modifications (like dislocation) can be taken back later on without other modifications (like color corrections) would be lost. Also, hidden tracks can be used for "event storage bins". Of course it can also be done with visible tracks, but hidden tracks are nicer for the user, plus it is ensured they are not modified.