May 16

bug

moveVertByIdAndDrawGraph - the moveVertById method is not working on self.graph

issue

You can only send objects in performSelector: withObject: .  To be more accurate you can only send variables of pointer type.

issue

The selector name is wrong. The compiler will give a warning for this but it will still run. 

note

Changing methods that are called in delegates in a lot of work. You have to change the method name in the implementation, the header, and the protocol definition. This would go faster if I could ever remember the command to switch between header and implementation. 

issue

Both the view controller method and the view method are out of date.

note

We have to set the viewId and pass the view id back

setting the view id occurs in the ViewController

passing the view id back occurs in the 

-(void)drawGraphAfterMovingVert:(int)viewId toXPos:(NSNumber*)endX toYPos:(NSNumber*)endY;

is this the right thing that I should be moving ?

note

in iOS there is no such thing as performSelector: withObject: withObject withObject: . two withObjects is the limit. 

question

is drawGraph getting hit after a move

answer

yes 

question

is removeSubviews getting hit

answer

removeSubviews is a graphWorldView method

issue

currently one of the breakpoints is just “setup”

goal

I want the graph cat to save. 

question

is the graph cat currently getting executed ?

answer

yes

it is sufficient to have parse save each of the verts

question: is the for loop in save in the Graph cat currently getting executed

bug and resolution: my save method in the PFVert class was not getting called because of a namespace collision.

style

Calls into my subclasses of PFObject should originate from PFVert

question

is blocking of saves of data that already exists in parse working ?

I can see from Parse that the Parse data model is not getting updated after I move a vert.

Question: is this happening because getVertById is returning nil ?

Answer: no. getVertById is returning a vert

note

When you write an NSLog statement it will always feel like you don’t need to write what method its in - after all its only going to be there for testing. 

goal

what I need is visibility into the number of Parse saves that get done. 

I can generalize this goal. 

note

Use __block variables to share storage.

bug

async issue

For some reason when I attempt to get the value of count I get out zero.

note

Apple's “debugging new in Xcode 6” from 2013 is way over my head.

day summary

I got changing the model to work.

GOT ASYNC PROBLEMS