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.
Is anyone else interested in this? So far I've sent the code to a few people, but no one has claimed the job yet. I've made it easier for you by going through all the apps and finding exactly where they crash. I even found out that a couple of them …
I've tried to solve my problem by using a rotation matrix to rotate the individual vertices, but the rotation doesn't seem to be working correctly. Here's my code:
- (void) calcRotation {
for( int i = 0; i < 8; i++ ) {
GLfloat v1 …
Thanks for the suggestion, but that book stopped at simple rotation and didn't explain it for 2-dimensions. I actually partially figured it out, but now I have a new problem (how to sum two rotations?).
MY SOLUTION:
Let's say you wanted to rotate …
I think I found the solution.
I guess global variables are never allowed to be assigned using other variables, so the solution is to make the variables members of your class and then assign them in some sort of initialization function.
What about this? http://developer.apple.com/library/ios/#documentation/UserExperience/Conceptual/SystemMessaging_TopicsForIOS/Articles/SendinganSMSMessage.html#//apple_ref/doc/uid/TP40010416-SW1
"In iOS 4.0 and later, you can send text messages fro…
Well, I actually got both ways working, so it must have been something else that was causing the EXC_BAD_ACCESS. But I have another question. Say the MyObject class has an object as one of it's properties, something like:
@interface MyObject : NSOb…
Didn't work. Based on my understanding of memory management, when I add 'newBackground' to the view it increases it's retain count to 2, so if I release it right away it still has a retain count of 1 and should still stick around.
The weird thing i…
Ok, I broke this down as simple as possible. I created a view-based app and added this code:
- (void)viewDidLoad {
MPMediaPropertyPredicate *podcastPred = [MPMediaPropertyPredicate predicateWithValue: [NSNumber numberWithInt: MPMediaTypePodcast] f…
Scratch my last post. I tried that method again and it didn't work this time. What seems to be working now is when I add this line to my original code:
[player setCurrentPlaybackTime: 0];
Baffling.
I just realized that if I completely quit the app (by double-clicking the home button and removing it from the apps-running-in-the-background list) and then re-launch, it works. Then at some point in the future it will stop working again. I can't fi…
YES!!!! After 7 hours of frustration. I got it to work. I opened my project's folder in finder, right-clicked on .xcodeproj file, selected "show package contents", then double-clicked the project.pbxproj to open it in an editor. In there, I found th…
Yay! I got it working by replacing:
CGPoint clickedPoint = [touch locationInView: [self.subviews objectAtIndex: 0]];
with:
CGPoint clickedPoint = [touch locationInView: [touch view]];
I'm still confused at to what was going on.
If I print a description of the view to the console (one for each case), I get:
>
and then
>
I don't know why it's so weird. I expect the frame to be (0 0; 1382 1652) in both cases. Any ideas?
I'm seem to be getting it. I'm now down to just two memory leaks, with the program working. But I'm confused about one thing. I have this code:
- (id) copyWithZone: (NSZone *) zone {
Section *sectionCopy = [[Section allocWithZone: zone] init];
se…
Thanks for the help guys. I think my properties are correct:
In Section.h I have:
@property (nonatomic, retain) NSMutableArray *tiles;
In Section.m I have:
- (void) dealloc {
[tiles release];
[super dealloc];
}
Elsewhere in my code, after the…
I was able to fix my problem, by removing the release calls to "sec" and "aTile". Of course, now I have memory leaks. Can anyone shed some light on what's happening? Thanks.
@interface Tile : NSObject {
BOOL pressed;
int row;
int column;
int section;
int value;
}
@interface Section : NSObject {
BOOL solved;
int sectionRow;
int sectionCol;
NSMutableArray *tiles;
}
for( int r = 1; r
Is there something special you have to do when you have two NSMutableArrays of custom objects nested within each other? I'm getting all kinds of data loss/overwriting. Plus, Instruments is telling me I have memory leaks even though I have all the ri…
Well, instead of applying the image directly to the background of the cell, I tried adding an image view and applying the image to that. Now it works. Don't know why. Strange behavior.
I think you're right. It seems to be crashing for some other reason. I just can't figure out what. Here's the log:
[Session started at 2010-11-20 16:20:25 -0800.]
2010-11-20 16:20:30.061 Fantasy Football 3[1376:207] *** Terminating app due to uncau…
I finally found an answer:
I replaced [self.view insertSubview: delegate.navController.view atIndex: 1];
with [[[UIApplication sharedApplication] keyWindow] addSubview: delegate.navController.view];
Now it seems to work.
