iGary
Sep 12, 06:22 AM
The "Today" show just said as fact, that Apple was releasing a movie service today.
Not saying they are right, but thought it was interesting it was reported as fact.
Not saying they are right, but thought it was interesting it was reported as fact.
Lancetx
Oct 6, 04:53 PM
Obviously YMMV, but I've never had any significant issues at all with AT&T's service in the nearly 2 1/2 years since I switched to them for the original iPhone. The same has continued since I upgraded to the 3GS as well. Verizon doesn't have the iPhone and won't be getting it anytime soon (if ever), so they're not on my radar screen anyway. And even if they did ever add the iPhone at some point, I doubt I'd ever switch because my own personal experience with Verizon's service several years ago was that it was absolutely dreadful.
mikerr
Apr 25, 12:28 PM
Still edge to edge glass like the ip4 = more cracked & shattered screens.
The 3G(s) were better designed with that metal ring to take the pain of a fall
instead of hitting the glass on edge
The 3G(s) were better designed with that metal ring to take the pain of a fall
instead of hitting the glass on edge
Evangelion
Nov 17, 11:28 AM
I think I just threw up in my mouth a little bit�.
Why? Even though Intel is faster right now, AMD still makes fine chips.
Why? Even though Intel is faster right now, AMD still makes fine chips.
Willis
Oct 17, 10:43 AM
so it's kind of a mixture here.
1. more capacity -> blu-ray
2. lower price -> hd-dvd
3. porn industry choses the cheapest format -> hd-dvd
Actually, the porn industry has gone with Blu-Ray.
1. more capacity -> blu-ray
2. lower price -> hd-dvd
3. porn industry choses the cheapest format -> hd-dvd
Actually, the porn industry has gone with Blu-Ray.
tim916
Sep 28, 07:40 PM
Oh i'm sure there will be LOTS of technology in the house.
I bet he'll be able to control everything via an app on his iPhone.
The house itself doesn't need to be HUGE. He can still apply a lot of technology into the house making it worth millions!
I'd wager that Jobs will avoid putting superfluous technology into the house. We know he loves simple and existing home control systems are usually anything but.
Filling a home wilth complex technology can actually have a negative effect on a home's value because it requires expensive servicing and, of course, becomes obsolete very quickly.
I bet he'll be able to control everything via an app on his iPhone.
The house itself doesn't need to be HUGE. He can still apply a lot of technology into the house making it worth millions!
I'd wager that Jobs will avoid putting superfluous technology into the house. We know he loves simple and existing home control systems are usually anything but.
Filling a home wilth complex technology can actually have a negative effect on a home's value because it requires expensive servicing and, of course, becomes obsolete very quickly.
wlh99
Apr 28, 10:08 AM
By the way, what's with 3rd person reference? the OP? you can call me Nekbeth or Chrystian, it's a lot more polite. Maybe you guys have a way to refer to someone , I don't know.
I appologize for that. I didn't recall your name. I was replying to KnightWRX, so I took a shorcut (original poster).
I won't do that any further.
I through together a simple program that I think does exactly as you want. It is a Mac version, but the different there is trival, and instead of a picker, it is a text field the user enters a time into for the timer duration. You will need to change the NSTextFields into UITextFields.
The bulk of the code is exactly what I posted before, but I modified the EchoIt method to work with an NSDate. I implemeted it in the appDelegate, and you are using your viewController. That doesn't change the code any, and your way is more correct.
I can email you the whole project as a zip if you want. It is about 2.5 meg. Just PM me your email address.
//
// timertestAppDelegate.m
// timertest
//
// Created by Warren Holybee on 4/27/11.
// Copyright 2011 Warren Holybee. All rights reserved.
//
#import "timertestAppDelegate.h"
@implementation timertestAppDelegate
@synthesize window, timeTextField, elapsedTimeTextField, timeLeftTextField;
- (void)applicationDidFinishLaunching:(NSNotification *)aNotification {
// Insert code here to initialize your application
}
-(IBAction)startButton:(id) sender {
// myTimer is declared in header file ...
if (myTimer!=nil) { // if the pointer already points to a timer, you don't want to
//create a second one without stoping and destroying the first
[myTimer invalidate];
[myTimer release];
[startDate release];
}
// Now that we know myTimer doesn't point to a timer already..
startDate = [[NSDate date] retain]; // remember what time this timer is created and started
// so we can calculate elapsed time later
NSTimeInterval myTimeInterval = 0.1; // How often the timer fires.
myTimer = [NSTimer scheduledTimerWithTimeInterval:myTimeInterval target:self selector:@selector(echoIt)
userInfo:nil repeats:YES];
[myTimer retain];
}
-(IBAction)cancelIt:(id) sender {
[myTimer invalidate];
[myTimer release]; // This timer is now gone, and you won't reuse it.
myTimer = nil;
}
-(void)echoIt {
NSDate *now = [[NSDate date] retain]; // Get the current time
NSTimeInterval elapsedTime = [now timeIntervalSinceDate:startDate]; // compare the current time to
[now release]; // our remembered time
NSLog(@"Elapsed Time = %.1f",elapsedTime); // log it and display it in a textField
[elapsedTimeTextField setStringValue:[NSString stringWithFormat:@"%.1f",elapsedTime]];
float timeValue = [timeTextField floatValue]; // timeValueTextField is where a user
// enters the countdown length
float timeLeft = timeValue - elapsedTime; // Calculate How much time is left.
NSLog(@"Time Left = %.1f",timeLeft); // log it and display it
[timeLeftTextField setStringValue:[NSString stringWithFormat:@"%.1f",timeLeft]];
if (timeLeft < 0) { // if the time is up, send "cancelIt:"
[self cancelIt:self]; // message to ourself.
}
}
@end
*edit:
If you like, later tonight I can show you how to do this as you first tried, by incrementing a seconds variable. Or wait for KnightWRX. My concern is accuracy of the timer. It might be off by several seconds after running an hour. That might not be an issue for your application, but you should be aware of it.
I appologize for that. I didn't recall your name. I was replying to KnightWRX, so I took a shorcut (original poster).
I won't do that any further.
I through together a simple program that I think does exactly as you want. It is a Mac version, but the different there is trival, and instead of a picker, it is a text field the user enters a time into for the timer duration. You will need to change the NSTextFields into UITextFields.
The bulk of the code is exactly what I posted before, but I modified the EchoIt method to work with an NSDate. I implemeted it in the appDelegate, and you are using your viewController. That doesn't change the code any, and your way is more correct.
I can email you the whole project as a zip if you want. It is about 2.5 meg. Just PM me your email address.
//
// timertestAppDelegate.m
// timertest
//
// Created by Warren Holybee on 4/27/11.
// Copyright 2011 Warren Holybee. All rights reserved.
//
#import "timertestAppDelegate.h"
@implementation timertestAppDelegate
@synthesize window, timeTextField, elapsedTimeTextField, timeLeftTextField;
- (void)applicationDidFinishLaunching:(NSNotification *)aNotification {
// Insert code here to initialize your application
}
-(IBAction)startButton:(id) sender {
// myTimer is declared in header file ...
if (myTimer!=nil) { // if the pointer already points to a timer, you don't want to
//create a second one without stoping and destroying the first
[myTimer invalidate];
[myTimer release];
[startDate release];
}
// Now that we know myTimer doesn't point to a timer already..
startDate = [[NSDate date] retain]; // remember what time this timer is created and started
// so we can calculate elapsed time later
NSTimeInterval myTimeInterval = 0.1; // How often the timer fires.
myTimer = [NSTimer scheduledTimerWithTimeInterval:myTimeInterval target:self selector:@selector(echoIt)
userInfo:nil repeats:YES];
[myTimer retain];
}
-(IBAction)cancelIt:(id) sender {
[myTimer invalidate];
[myTimer release]; // This timer is now gone, and you won't reuse it.
myTimer = nil;
}
-(void)echoIt {
NSDate *now = [[NSDate date] retain]; // Get the current time
NSTimeInterval elapsedTime = [now timeIntervalSinceDate:startDate]; // compare the current time to
[now release]; // our remembered time
NSLog(@"Elapsed Time = %.1f",elapsedTime); // log it and display it in a textField
[elapsedTimeTextField setStringValue:[NSString stringWithFormat:@"%.1f",elapsedTime]];
float timeValue = [timeTextField floatValue]; // timeValueTextField is where a user
// enters the countdown length
float timeLeft = timeValue - elapsedTime; // Calculate How much time is left.
NSLog(@"Time Left = %.1f",timeLeft); // log it and display it
[timeLeftTextField setStringValue:[NSString stringWithFormat:@"%.1f",timeLeft]];
if (timeLeft < 0) { // if the time is up, send "cancelIt:"
[self cancelIt:self]; // message to ourself.
}
}
@end
*edit:
If you like, later tonight I can show you how to do this as you first tried, by incrementing a seconds variable. Or wait for KnightWRX. My concern is accuracy of the timer. It might be off by several seconds after running an hour. That might not be an issue for your application, but you should be aware of it.
Anthony T
Apr 16, 10:10 AM
A quick read through this thread is proof of why I normally don't bother reading or posting here.
Almost everyone has posted that they feel the next iPhone could look something like this...
...which is completely ridiculous based on logic and common sense. But it has been my experience that Macrumors forums and "logic" and "common sense" cannot exist in the same place at the same time.
Memory also seems to be a problem around here. For example, Apple's breakthrough smartphone that changed phones for forever, was completely and totally redesigned after its first year, because the design was incredibly flawed.
To not understand the significance of this, is really to forfeit your opinion on what Apple will or will not do. You CANNOT logically state that Apple would return to an aluminum iPhone (no matter how sexy it might look), after having already moved away from it.
2 straight years, the iPhone 3G and 3GS have unibody plastic design. The SAME one. This is not a coincidence, or laziness, or any other 4th grade opinion....its what the iPhone is. It's not going to change.
The most Apple will do with the design, is make it a little taller to accommodate more pixels, but the design will remain. They may offer a few more colors, or they may not.
Plastic, Unibody iPhones are here to stay. To state otherwise, is to fantasize, and ignore reality. (which is fine, just acknowledge it please).
Ok, Mr. Intelligent. It's been 3 years since the original iPhone launched. Perhaps Apple found a way to make a phone out of aluminum or a similar material, without affecting performance? Also, the iPad is made out of aluminum, yet it uses 3G service. You're acting like you know for sure what will happen, and you don't. None of us do.
Almost everyone has posted that they feel the next iPhone could look something like this...
...which is completely ridiculous based on logic and common sense. But it has been my experience that Macrumors forums and "logic" and "common sense" cannot exist in the same place at the same time.
Memory also seems to be a problem around here. For example, Apple's breakthrough smartphone that changed phones for forever, was completely and totally redesigned after its first year, because the design was incredibly flawed.
To not understand the significance of this, is really to forfeit your opinion on what Apple will or will not do. You CANNOT logically state that Apple would return to an aluminum iPhone (no matter how sexy it might look), after having already moved away from it.
2 straight years, the iPhone 3G and 3GS have unibody plastic design. The SAME one. This is not a coincidence, or laziness, or any other 4th grade opinion....its what the iPhone is. It's not going to change.
The most Apple will do with the design, is make it a little taller to accommodate more pixels, but the design will remain. They may offer a few more colors, or they may not.
Plastic, Unibody iPhones are here to stay. To state otherwise, is to fantasize, and ignore reality. (which is fine, just acknowledge it please).
Ok, Mr. Intelligent. It's been 3 years since the original iPhone launched. Perhaps Apple found a way to make a phone out of aluminum or a similar material, without affecting performance? Also, the iPad is made out of aluminum, yet it uses 3G service. You're acting like you know for sure what will happen, and you don't. None of us do.
twoodcc
May 8, 11:01 PM
It is folding at stock speed with threading turned off and it is doing big normal units at 3 minutes per frame. For some reason it hasn't gotten any -bigadv units since I set it up like this. It is using all 6 cores at least.
awe man. well at least you have it going. it's too bad you don't have it running bigadv units though.
3.7 is still really good, hope it stays there ok.
thanks. yeah i can live with 3.7. i just hope it stays stable
I'm starting to think that gpu's are the only way to go from now on; you tend not to lose wu's on them and if you do it only takes a couple of hours to catch up to where you were on the last one, not the day or 2 like bigadv units.
Hope that Alienware rig works ok now, can you get anymore gpu's in it?
yeah that's true, but the gpus use more power and so then more heat than the bigadv units. with bigadv, you get more points/power usage, which is a big deal. but they can be a headache.
thanks. no, the alienware only holds 2 double wide gpus. now i have to in there and they are both going.
awe man. well at least you have it going. it's too bad you don't have it running bigadv units though.
3.7 is still really good, hope it stays there ok.
thanks. yeah i can live with 3.7. i just hope it stays stable
I'm starting to think that gpu's are the only way to go from now on; you tend not to lose wu's on them and if you do it only takes a couple of hours to catch up to where you were on the last one, not the day or 2 like bigadv units.
Hope that Alienware rig works ok now, can you get anymore gpu's in it?
yeah that's true, but the gpus use more power and so then more heat than the bigadv units. with bigadv, you get more points/power usage, which is a big deal. but they can be a headache.
thanks. no, the alienware only holds 2 double wide gpus. now i have to in there and they are both going.
2 Replies
Jul 21, 01:44 PM
Oh my god...
did Apple seriously just make pointing fingers apart of their campaign?
I thought they were above that!
I understand that it's unfair that the other companies do that and all, but Apple really doesn't need to stoop to their level, do they?
Above that? HA!
Looks like someone forgot about the Mac vs PC ads. ;)
It would be nice if Apple actually ACTED like an adult and not like it's own fanboi. :-\
did Apple seriously just make pointing fingers apart of their campaign?
I thought they were above that!
I understand that it's unfair that the other companies do that and all, but Apple really doesn't need to stoop to their level, do they?
Above that? HA!
Looks like someone forgot about the Mac vs PC ads. ;)
It would be nice if Apple actually ACTED like an adult and not like it's own fanboi. :-\
aristobrat
Oct 6, 03:28 PM
i live in the san francisco bay area ---berkeley.
<snip>
I really love my iphone and am sorely regretting that i'm going to have to give it up because of att's unacceptable lack of reliable service
Yeah, you live in one of the two cities that AT&T repeatedly admits it's screwed up ... SF and NYC. :eek:
A little over two weeks ago, AT&T started turning on 3G coverage on their 850mhz frequency, which has greater range. Hopefully that will impact your service positively.
http://www.phonescoop.com/news/item.php?n=4718
<snip>
I really love my iphone and am sorely regretting that i'm going to have to give it up because of att's unacceptable lack of reliable service
Yeah, you live in one of the two cities that AT&T repeatedly admits it's screwed up ... SF and NYC. :eek:
A little over two weeks ago, AT&T started turning on 3G coverage on their 850mhz frequency, which has greater range. Hopefully that will impact your service positively.
http://www.phonescoop.com/news/item.php?n=4718
longofest
Oct 19, 10:26 AM
1.5% woo hoo!! Thats quite a climb!
Indeed. If you look at it a different way, it is a 33% increase year over year for Apple's market share numbers.
How I got to 33%:
% increase_________1.5
---------------- = ---- = 32.6%
old market share____4.6
Indeed. If you look at it a different way, it is a 33% increase year over year for Apple's market share numbers.
How I got to 33%:
% increase_________1.5
---------------- = ---- = 32.6%
old market share____4.6
iJohnHenry
Apr 16, 05:08 PM
Yes, I do believe Merriam Webster is still up and running...
This is no value to me, if you consider your position to be narrow-mind, and not an abomination, sorry...., affront.
This is no value to me, if you consider your position to be narrow-mind, and not an abomination, sorry...., affront.
Surreal
Mar 28, 03:31 PM
I voted this negative because Apple won't accept certain apps for doing reasonable things. "dangerous" if done incorrectly, but reasonable.
Until devs can do all of the low level things they need to, this is a bad move.
Until devs can do all of the low level things they need to, this is a bad move.
dalvin200
Sep 12, 04:42 AM
would be but were on BST (GMT+1) matey.
its a 5PM GMT start
so using your formula above 5PM + 1 = 6PM BST :)
its a 5PM GMT start
so using your formula above 5PM + 1 = 6PM BST :)
Lord Blackadder
Aug 8, 01:25 AM
]
I would argue that hybrids are a long term solution.More so plug in hybrids I think are a longer term solution. It allows people to charge for their daily stuff at home. Then for longer trips you have an on board generator of some type to continue to charge the batteries.
So if that best diseal was a hybrid it would have even a longer range and better gas mileage.
Plug-in hybrids put additional strain on the power grid, a strain it cannot currently handle on a large scale. So plugin electrics are not ready for large-scale adoption yet. If electric cars are to be the future, our power grid needs to be made much, much higher capacity AND a lot greener.
Lifestyle choices are always going to trump technology in terms of impact on the environment and saving fuel. If everyone made it a point to buy a more efficient car the next time they buy a vehicle, the impact would be truly staggering. If everyone bought a 10% more efficient car, the fuel savings would add up fast.
We can't rely on technology to pick up the slack and protect us from our own destructive lifestyles. We need to be proactive and make changes, even sacrifices. I admit I still love my sportscars, but they are the least of our worries - it's all the big SUV daily drivers and trucks that are killing us.
I would argue that hybrids are a long term solution.More so plug in hybrids I think are a longer term solution. It allows people to charge for their daily stuff at home. Then for longer trips you have an on board generator of some type to continue to charge the batteries.
So if that best diseal was a hybrid it would have even a longer range and better gas mileage.
Plug-in hybrids put additional strain on the power grid, a strain it cannot currently handle on a large scale. So plugin electrics are not ready for large-scale adoption yet. If electric cars are to be the future, our power grid needs to be made much, much higher capacity AND a lot greener.
Lifestyle choices are always going to trump technology in terms of impact on the environment and saving fuel. If everyone made it a point to buy a more efficient car the next time they buy a vehicle, the impact would be truly staggering. If everyone bought a 10% more efficient car, the fuel savings would add up fast.
We can't rely on technology to pick up the slack and protect us from our own destructive lifestyles. We need to be proactive and make changes, even sacrifices. I admit I still love my sportscars, but they are the least of our worries - it's all the big SUV daily drivers and trucks that are killing us.
ulbador
Apr 26, 09:59 AM
The point dejo was trying to make, is that you are missing a VERY basic Objective C (well, any language really) fundamental.
This:
- (void) cancelIt:(NSTimer*)timer
does NOT create an object.
It's simply a map to say "When I call this method, I will pass in an existing timer object". It is still your responsibility to allocate/initialize a timer and then pass that into your method. Simply using the selector as you are doing wouldn't accomplish this.
At some point you would have to do something like:
[self cancelIt:MyExistingAndValidTimerObject];
This:
- (void) cancelIt:(NSTimer*)timer
does NOT create an object.
It's simply a map to say "When I call this method, I will pass in an existing timer object". It is still your responsibility to allocate/initialize a timer and then pass that into your method. Simply using the selector as you are doing wouldn't accomplish this.
At some point you would have to do something like:
[self cancelIt:MyExistingAndValidTimerObject];
dieselpower44
Jul 21, 10:09 AM
The iPhone 4 works marvelously well. It is the most reliable iPhone I have ever owned, and the previous versions set a high standard to match. I am perfectly able to duplicate the issue (in my office, where the signal is poor) but as far as I can tell it has only resulted in one dropped call (while the 3GS dropped more due to holding a less reliable poor signal).
So if Apple truly had released a horrible product I could agree with you. Instead I'm simply left suspecting that you don't own the thing and are simply content to tell other people how the device works anyway.
Completely incorrect, I have always been an Apple customer. I just recently bought an i7 iMac and own a Macbook pro, an iPod touch and an iPhone 3G. I waited in line for the iPhone 4, and I absolutely love the thing to bits. It's the fastest, most awesome phone I've ever owned. But what annoys me is that you have to agree that this is the most serious problem relating to signal attenuation ever been seen. I mean yes, it has been blown out of proportion by the media but when you get down and actually test it out in different signal strength areas, you definitely notice it pretty severely.
But what annoys me the most, is Apple's "couldn't give a s***, let's point out other people's similar mistakes." Apple has never been like this before. Jobs may have saved the company but he's also going to ruin it with this attitude. Wozniak would have recalled the phones.
So if Apple truly had released a horrible product I could agree with you. Instead I'm simply left suspecting that you don't own the thing and are simply content to tell other people how the device works anyway.
Completely incorrect, I have always been an Apple customer. I just recently bought an i7 iMac and own a Macbook pro, an iPod touch and an iPhone 3G. I waited in line for the iPhone 4, and I absolutely love the thing to bits. It's the fastest, most awesome phone I've ever owned. But what annoys me is that you have to agree that this is the most serious problem relating to signal attenuation ever been seen. I mean yes, it has been blown out of proportion by the media but when you get down and actually test it out in different signal strength areas, you definitely notice it pretty severely.
But what annoys me the most, is Apple's "couldn't give a s***, let's point out other people's similar mistakes." Apple has never been like this before. Jobs may have saved the company but he's also going to ruin it with this attitude. Wozniak would have recalled the phones.
KnightWRX
Apr 26, 09:37 AM
Oh please don't be so smart. What you say means to lose the pixel density of Retina Display. Would you want that?
Considering the treshold is 300 PPI for "Retina" at 12 inches of distance and that the iPhone 4 has 326 PPI at 3.5", yes I say we can afford to lose a few PPI for a bigger screen. In the end, it will still be "Retina" (as in you can't distinguish individual pixels at a normal viewing distance).
Anyway, it's not like a screen being "Retina" or not has any effect on a developer. If both screens are 960x640, the developer has nothing to change with his code or art at all. It will all work, no matter the actual screen size. What does being a developer even have to do with losing some PPI ? Nothing. Nothing at all.
Considering the treshold is 300 PPI for "Retina" at 12 inches of distance and that the iPhone 4 has 326 PPI at 3.5", yes I say we can afford to lose a few PPI for a bigger screen. In the end, it will still be "Retina" (as in you can't distinguish individual pixels at a normal viewing distance).
Anyway, it's not like a screen being "Retina" or not has any effect on a developer. If both screens are 960x640, the developer has nothing to change with his code or art at all. It will all work, no matter the actual screen size. What does being a developer even have to do with losing some PPI ? Nothing. Nothing at all.
Sounds Good
Apr 21, 09:23 PM
When is Windows 8 due out?
Davowade
Apr 7, 01:15 AM
:eek: NICE!!! Man, I am green with jealous rage. Makes my 40D, kit lens, and 50 1.8 seem so, so pathetic.
Thanks. Sadly this all belongs to work, but it should team pretty well with my personal 550D.
Thanks. Sadly this all belongs to work, but it should team pretty well with my personal 550D.
JAT
Apr 6, 04:50 PM
Considering it was released on April 5 (that's today), you either:
rtdunham
Oct 10, 10:34 PM
i made a quick mockup of what it could be like, i left out some details. I changed the dvd icon to a mail/gtube one(youtube) because it supossdly has wi-fi.....opinions?
http://img223.imageshack.us/img223/374/ipodmockzr0.jpg
...and an integrated spell-checker! :D
http://img223.imageshack.us/img223/374/ipodmockzr0.jpg
...and an integrated spell-checker! :D
EssentialParado
Jan 9, 04:57 PM
Thanks for posting the link guys. Can't believe it isn't posted on the main macrumor page yet. But what I CANNOT believe is that Apple spoiled it themselves!! AR%GH.
Please, whoever adds the link to the event, DIRECT link to the event page, DO NOT go to /appleevents/
Please, whoever adds the link to the event, DIRECT link to the event page, DO NOT go to /appleevents/
No comments:
Post a Comment