* - your email address will never be displayed on the site.
Topic History of: ZigVersion 1.2 Beta2 Max. showing the last posts - (Last post first)
Author
Message
John
Yeah, I agree - it is missed. Perhaps just giving the folder some treatment to show that files in it have been changed (like a color change or something) rather than putting an "M" in the column.
I don't use "Changed Files" at all because it doesn't retain my file tree viewstate when I toggle it off, forcing me to reopen folders all the time. Instead, I just use "Check In" to see if files have been changed and cancel if I'm not really ready to do the commit.
jg
That's really unfortunate, I don't want to leave "Changed Files" checked all the time and without those indicators there displaying changes in the hierarchy, I don't know when things change.
I hope you decide to put it back in.
eriks
When we added the 'Changed Files' feature in 1.1, we went ahead and removed the folder showing status of children feature. This was sometimes confusing since there was no way to tell if the folder itself was modified (properties modified on it), and the new feature seemed like a better way to solve the problem.
jg
I'm seeing status not always percolate up to containers. More often it seems to happen with bundles but also some folders.
Let me know if there's some way I can help you track this down. Unfortunately I don't have any public repos to share with you to provide you with surety that this is reproducable. Otherwise simple modify a .nib or even settings in a project. Run Update and note that the containers do not display that there are modified items contained within.
eriks
ZigVersion 1.2 Beta2 is up. This release fixes some of the issues encountered in 1.2beta1. See the release notes for more details.
