Closed emadd closed 13 years ago
After reviewing the stackScrollViewController class, I saw that you guys were relying on tags to manage the removal of views from the stack. I too am relying on tagging for certain views and view cells. I modified your code to assign tags to i*1000 and that resolved the problem.
I'm having a strange problem. Half of the view controllers launched with startStackView:YES work perfectly when continuing to add other view controllers to the stack. The other half, which are very similar in design, cause strange behavior that suggests the StackScrollView controller is losing track of how many view controllers are in the stack.
Example: Adding Browse as the startStackView, Browse adds Company. Selecting a different record in Browse removes the previously selected Company view from the stack and the new one appears in the correct place. If I add Saved as the startStackView and then select a Company record, I again add Company to the stack. However, when I select a different record on Saved, the stackScroll controller does NOT remove the previously selected Company view. They just keep piling up.
I can't think of any reason why these particular controllers are behaving the way they are. Instruments doesn't show any memory leaks or anything else unusual. Any ideas?