Please do not post the same thing multiple times. The board software automatically flags certain posts as needing moderator attention. This happens the most often for new users. I'm pretty sure this is made clear at the time you attempt to post. Posting the same thing over and over again just makes that many more posts the moderators have to weed through later. This makes us sad. Don't make us sad. If your post/thread doesn't appear, just wait a while. Don't post it again. If it hasn't shown up by the next day, then you can try again. I normally go through posts in the mornings, and try to check a few times throughout the day, but I'm not here 24/7. There will typically be a significant delay before posts are approved. Just be patient.
I can't seem to get the built in animations to work when designing this container view controller. I have tried adding everything programmatically and have tried using nibs for all of the child view controllers. No joy.
Does this project reflect this, and does anyone have any input into what I am doing wrong? Or is my installation of the SDK on my comp corrupted and I should reinstall everything. lol.
Actually I have found tons of posts, relevant code, and books on the subject. I have made 3 different example projects based around the one I have on github, trying various techniques found in these posts, code and books.
However after looking at it, I don't see what the difference is between the setup of childViewControllers and their parentViewController between MH and mine example.
I can set the duration to 5 seconds and it still just instantly transitions to the next view controller calling the completion block in less than a second.
and you cannot set a UIViewAnimationOptionTransition, and include an animation block at the same time!
I am surprised no one caught this. Could of saved me 2 days. Albeit I was working on other stuff, but it was because I had already wasted enough time looking through documentation, example code etc.
Another set of eyes definitely would of helped...
Anyways, I hope others that have this stupid mistake will find my thread.
and you cannot set a UIViewAnimationOptionTransition, and include an animation block at the same time!
I am surprised no one caught this. Could of saved me 2 days. Albeit I was working on other stuff, but it was because I had already wasted enough time looking through documentation, example code etc.
Another set of eyes definitely would of helped...
Anyways, I hope others that have this stupid mistake will find my thread.
Peace,
Joe
I'm glad you found the solution to your problem.
I'm a lousy proofreader, and not likely to catch something like using a wrong, but similarly-named constant.
In the future, don't create multiple threads on the same subject. It's annoying, and makes the admins crazy. (me too, but I can't ban you for it...)
Regards,
Duncan C WareTo
Animated GIF created with Face Dancer, available for free in the app store.
I'm a lousy proofreader, and not likely to catch something like using a wrong, but similarly-named constant.
In the future, don't create multiple threads on the same subject. It's annoying, and makes the admins crazy. (me too, but I can't ban you for it...)
Sorry, I didn't want to take over your thread honestly, as it was about your experience with the new containment apis in iOS 5. Since mine was more problem based, and more specifically with the fact that I could not get animations working, I decided to start a new thread.
I believe it was justified (could be wrong as I can't please everyone). I have started asking questions on other relevant threads before and have been told not to mess with them and to start new one's.
Truthfully I am tired of being pushed around (not the first time I have come to these forums!). Stop it, lol. If I don't see a relevant thread from now on, or I don't receive any help what so ever (i.e. they either don't respond in 3 days, don't have anything intelligent to say, or tell me to just look at the docs which can easily be said on any thread), or they tell me in various ways to shove it, I am going to start my own thread.
And for the record I love Apple's documentation, and it is usually the first place I look. However, it does not always strike a cord I guess you could say.
Thank you for at least being polite and professional,
Sorry, I didn't want to take over your thread honestly, as it was about your experience with the new containment apis in iOS 5. Since mine was more problem based, and more specifically with the fact that I could not get animations working, I decided to start a new thread.
I believe it was justified (could be wrong as I can't please everyone). I have started asking questions on other relevant threads before and have been told not to mess with them and to start new one's.
Truthfully I am tired of being pushed around (not the first time I have come to these forums!). Stop it, lol. If I don't see a relevant thread from now on, or I don't receive any help what so ever (i.e. they either don't respond in 3 days, don't have anything intelligent to say, or tell me to just look at the docs which can easily be said on any thread), or they tell me in various ways to shove it, I am going to start my own thread.
And for the record I love Apple's documentation, and it is usually the first place I look. However, it does not always strike a cord I guess you could say.
Thank you for at least being polite and professional,
Joe
Sorry that you're feeling bullied. That was not my intention. And you're right that it's usually better to start a new thread rather than attaching to an existing thread, unless what you are posting is directly related (e.g. "I'm having the same problem you report, with the following differences...")
If you do post a new thread on the same subject, it helps to post a notice in both places referring to the other thread
("I decided my question should really be in it's own thread, so I created a new one. It's at the following link..."
and
"I started asking about topic XYZ in another thread, but decided it should be a separate thread. The other thread is at the following link...")
That way people can find the whole discussion, and don't waste time thinking "wait a minute, didn't I read posts on this exact subject just yesterday..."
Anyway, enough on that.
In general, I agree that Apple's documentation is good. However, they have been getting badly behind, starting with Xcode 4.0. There are still large sections of the docs that describe the old, no-longer-relevant Xcode 3 way of doing things, and every iota of Xcode is totally and completely different in Xcode 4, so the old docs are worthless.
There are also huge holes in the docs when it comes to iOS 5 APIs, and an alarmingly large number of errors.
Regards,
Duncan C WareTo
Animated GIF created with Face Dancer, available for free in the app store.
Sportyguy_007
Posts: 8New Users
Replies
Actually I have found tons of posts, relevant code, and books on the subject. I have made 3 different example projects based around the one I have on github, trying various techniques found in these posts, code and books.
However after looking at it, I don't see what the difference is between the setup of childViewControllers and their parentViewController between MH and mine example.
I can set the duration to 5 seconds and it still just instantly transitions to the next view controller calling the completion block in less than a second.
And it sure as hell does not flip from right.
This is driving me crazy, and I only ask for another set of eyes on the subject!
Best,
Joe
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like AwesomeShould use :
instead of:
and you cannot set a UIViewAnimationOptionTransition, and include an animation block at the same time!
I am surprised no one caught this. Could of saved me 2 days. Albeit I was working on other stuff, but it was because I had already wasted enough time looking through documentation, example code etc.
Another set of eyes definitely would of helped...
Anyways, I hope others that have this stupid mistake will find my thread.
Peace,
Joe
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like AwesomeI'm a lousy proofreader, and not likely to catch something like using a wrong, but similarly-named constant.
In the future, don't create multiple threads on the same subject. It's annoying, and makes the admins crazy. (me too, but I can't ban you for it...)
Duncan C
WareTo
Animated GIF created with Face Dancer, available for free in the app store.
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like AwesomeI believe it was justified (could be wrong as I can't please everyone). I have started asking questions on other relevant threads before and have been told not to mess with them and to start new one's.
Truthfully I am tired of being pushed around (not the first time I have come to these forums!). Stop it, lol. If I don't see a relevant thread from now on, or I don't receive any help what so ever (i.e. they either don't respond in 3 days, don't have anything intelligent to say, or tell me to just look at the docs which can easily be said on any thread), or they tell me in various ways to shove it, I am going to start my own thread.
And for the record I love Apple's documentation, and it is usually the first place I look. However, it does not always strike a cord I guess you could say.
Thank you for at least being polite and professional,
Joe
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like AwesomeSorry that you're feeling bullied. That was not my intention. And you're right that it's usually better to start a new thread rather than attaching to an existing thread, unless what you are posting is directly related (e.g. "I'm having the same problem you report, with the following differences...")
If you do post a new thread on the same subject, it helps to post a notice in both places referring to the other thread
("I decided my question should really be in it's own thread, so I created a new one. It's at the following link..."
and
"I started asking about topic XYZ in another thread, but decided it should be a separate thread. The other thread is at the following link...")
That way people can find the whole discussion, and don't waste time thinking "wait a minute, didn't I read posts on this exact subject just yesterday..."
Anyway, enough on that.
In general, I agree that Apple's documentation is good. However, they have been getting badly behind, starting with Xcode 4.0. There are still large sections of the docs that describe the old, no-longer-relevant Xcode 3 way of doing things, and every iota of Xcode is totally and completely different in Xcode 4, so the old docs are worthless.
There are also huge holes in the docs when it comes to iOS 5 APIs, and an alarmingly large number of errors.
Duncan C
WareTo
Animated GIF created with Face Dancer, available for free in the app store.
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like Awesome