DocOz found a fat-zapper?

[DocOz: Fact or Fiction?]

Fact or Fiction?
You can lose 20-lbs w/out working out?

DocOz's Response: FACT!


DocOz devoted an entire episode to this exciting discovery.
Doctors and surgeons aren't talking about this, bc they make money if your over-weight.


View how to Drop 20 in 20-days -> http://www.oilyoutee.com/Droz/myth/buster.episode









[DocOz Blog]
June 12, 2014
Archives > http://www.oilyoutee.com/Droz/myth/buster.episode







to alter message settings with Member Update Systems
write 'stop' to 9167 ROAD 177-O a k w o o d_OH_45873 or http://www.oilyoutee.com/kdnr/sgjr.ekkcik















I'm trying to pass information back and forward through 4 VC in a NavController. I can set all the delegates and pass information fine going forward. What I don't get is where I should be calling the methods to pass stuff backwards when the back button is pressed. Should I be calling it from the "about to pop" VC in something like
@RobertNunn Your best off starting a new Question about this. It makes it easier to reply and add code etc.. Matt Price Apr 10 '12 at 15:43
Do we also have to put an @class ViewControllerB; above the @protocol definition? Without it I get an "Expected type" error on ViewControllerB in the line: - (void)addItemViewController:(ViewControllerB *)controller
Very nice guide. Helped me a lot. Thanks for sharing. his works great. As alan-p says, don't forget to write @class ViewControllerB; above the protocol otherwise I had a problem with specifying the protocols. I also had the [at]class error, but it also didn't accept the @interface ViewControllerA : UIViewController line. If you also have this problem (to tell ViewControllerA to conform to the protocol), then click the link here. I used the answer of the user Everything is awesome except some typos like initWithNib=@"ViewControllerB" bundleisSomethingEnabled is BOOL and works without throwing an "issue" without the pointer symbol, *, but I could not edit the answer because I could not think of how to edit at least 6 characthers zerowords Jun 3 '13 at 19:30
Passing Data Forward using Segue's (4.) first one works also for views which are embedded in a navigation controller. :- If we specify a class method in viewControllerB and then return the required string from that method, then can't this approach substitute the delegate method or is there any drawback to using class method ? I'm not 100% sure, as i'm still learning myself. However i'd say that what you suggest would make classes class methods are really meant to be used as "helper" methods. essentially just a way to quickly do some routine task or get some info about the class. if you look through the apple documentation at the nsstring class, that is a perfect example of its use. essentially "hey class, give me back something useful i can use." @Matt Price Your answer you posted is just a long winded version of the same thing i stated a year or so ago. why you felt the need to delete it is beyond me. unfortunately some of us with day jobs can't sit and type out code examples all day. DoS Sep 6 '13 at 17:52
@Max look into nsnotificationcenter as a pseudo alternative to delegates and protocols. this seems to be the common trend and the direction apple is moving in. DoS Sep 6 '13 at 17:55
you don't need delegates for passing back, just use unwind. malcolmhall Sep 27 '13 at 3:30
Thank you so much for posting thGreat simple example to begin my understanding of how delegates work in Obj C KateMak Jan 2 at 5:11

IMHO, as soon as you start passing things around in complicated ways, I think of two things. One, you better have a great testing framework... And two, I'd consider using notifications. Michael Graff Mar 7 at 14:46

When I put "viewControllerB.delegate = self;" in ViewControllerB I'm getting an error. Assigning to 'id<ViewControllerBDelegate>' from incompatible type 'ViewControllerB *const __strong', I'm not sure what I'm doing wrong. Can anyone help? Plus I had to change: initWithNib --> initWithNibName. Gerard Grundy Mar 28 at 21:21

for Passing Data back using Segue's, i think step 6 must change. can you please show me the solution? nmokkary Apr 26 at 10:08

Delegate and block is iOS programming style or taste andyqee May 13 at 14:08

@MattPrice please tell why not use the same "forward data method" to pass data back. S.J May 30 at 16:08

@S.J I'm no expert but, you would have to keep reference to ViewControllerA in ViewControllerB in order to set the property on ViewControllerA. This makes the views tightly coupled which is bad practice IMO. Matt Price May 30 at 22:13