Surf Monkey
Mar 17, 12:26 PM
I think its the kid's responsibility here. The OP had every intention of paying for his purchase, but the cashier dropped the ball big time. When you take on a job, you assume the responsibilities that come with it. Making a mistake that big will have consequences. I would hate to have someone that makes mistakes like that working for me.
Hogwash. The cashier made a mistake. At the moment the mistake was made ONE party knew about it and one didn't. The OP, who knew that a mistake had been made said nothing about it. He should have. People can defend this guy all they want, but the fact of the matter is that he deserves the flames he's getting. An ethical person would have said "you forgot to charge my card" and paid the outstanding balance.
Hogwash. The cashier made a mistake. At the moment the mistake was made ONE party knew about it and one didn't. The OP, who knew that a mistake had been made said nothing about it. He should have. People can defend this guy all they want, but the fact of the matter is that he deserves the flames he's getting. An ethical person would have said "you forgot to charge my card" and paid the outstanding balance.
balamw
Apr 28, 07:37 PM
I first started a new project in order to avoid confusion and made some changes, the result is what I think " a working timer " with start, stop and reset buttons.
Maybe now you can go back and realize that you could have saved yourself and the rest of us a lot of time and effort by adhering to the recommendations from the links I posted. (Seriously, read them.)
Be specific. Be complete. Post complete, compilable code that demonstrates your problem. (If you need to, make a separate toy app, divide and conquer).
This is part of the "step back" that everyone was telling you to do early on, and is a basic skill for all kinds of troubleshooting. By breaking down the problem and explaining it to someone else you will often get an epiphany of your own. Like:
If I see the code now it seems a bit obvious why the timer never stopped before.
If the solution was handed to you it wouldn't (a) be that obvious [because you wouldn't understand it] and (b) wouldn't be exactly what you want.
For obvious reasons I'm not posting it and if some of you wonder why, it's for same reasons nobody posted the complete working code despite being able to make a timer in less than 3 minutes. (yes, I know it's because you think it would not help me and I understand)
I still don't think you understand the give and take of being a full participant in a forum like this.
It's your choice alone whether to add to the general knowledge pool or not. That's very different than responding to an ill-defined request for code.
For example, here's a thread I started earlier this month: http://forums.macrumors.com/showthread.php?t=1133446 I was playing with some code from various tutorials that was no longer functional, found a way to fix it and chose to give that solution back to the 'net and it was immediately useful for another user.
B
Maybe now you can go back and realize that you could have saved yourself and the rest of us a lot of time and effort by adhering to the recommendations from the links I posted. (Seriously, read them.)
Be specific. Be complete. Post complete, compilable code that demonstrates your problem. (If you need to, make a separate toy app, divide and conquer).
This is part of the "step back" that everyone was telling you to do early on, and is a basic skill for all kinds of troubleshooting. By breaking down the problem and explaining it to someone else you will often get an epiphany of your own. Like:
If I see the code now it seems a bit obvious why the timer never stopped before.
If the solution was handed to you it wouldn't (a) be that obvious [because you wouldn't understand it] and (b) wouldn't be exactly what you want.
For obvious reasons I'm not posting it and if some of you wonder why, it's for same reasons nobody posted the complete working code despite being able to make a timer in less than 3 minutes. (yes, I know it's because you think it would not help me and I understand)
I still don't think you understand the give and take of being a full participant in a forum like this.
It's your choice alone whether to add to the general knowledge pool or not. That's very different than responding to an ill-defined request for code.
For example, here's a thread I started earlier this month: http://forums.macrumors.com/showthread.php?t=1133446 I was playing with some code from various tutorials that was no longer functional, found a way to fix it and chose to give that solution back to the 'net and it was immediately useful for another user.
B
slipper
Apr 25, 11:47 AM
Though i wanted a 4" screen, a 3.7" screen is a great compromise. I like the fact that it fits the current form factor.
BTW those images look like cheesy photoshop mock-ups
BTW those images look like cheesy photoshop mock-ups
Detlev
Mar 28, 03:42 PM
Ooh the arguments are getting heated up in this thread :D
Thought I'd offer a light refreshment.
Nice. You've been waiting to use that, haven't you?
Thought I'd offer a light refreshment.
Nice. You've been waiting to use that, haven't you?
more...
LightSpeed1
Apr 29, 04:10 PM
Let's hope this isn't the last change...
I disliked a few changes in the shortcuts in the track pad gestures...
Glad to know I'm not the only one.
I disliked a few changes in the shortcuts in the track pad gestures...
Glad to know I'm not the only one.
Muadib
Oct 3, 10:32 AM
V. L. C.
don't tell me you haven't use this magnificient software? (on mac, linux and win32)
don't tell me you haven't use this magnificient software? (on mac, linux and win32)
more...
Chundles
Nov 16, 12:34 PM
please no page 1 vs page 2 comments... :)
Rose McGowan, often remembered
more...
Rose McGowan- She made an ugly
Rose Mcgowan And Marilyn.
more...
Rose McGowan in a daring
dork Marilyn Manson,
more...
McGowan was subsequently cast
Marilyn Manson and Rose
more...
asked of Rose McGowan that
Actress Rose McGowan has
more...
See another picture of Rose.
rose mcgowan and marilyn
Rose McGowan plays Marique,
wlh99
Apr 26, 08:59 PM
After that I implement a Cancel method pointing to sender (button)
So, my goal is to use 1 start button and 1 cancel button.. and just do their actions. I have set up a the start button to start both timers, obviously both start their countdown at the same time which is not good.
I want to tell one timer to start and if I press cancel, invalidate it. Then If I press start again, call the second timer. (I do this because I read that you can't reuse a timer after you invalidate it).
Some people have suggested to use Booleans like true or false, or conditions. What do you think?
What if after pressing the start button, you create a timer and start it. Then pressing the cancel button invalidates and releases it. Then pressing the start button would create another timer, using the same pointer.
Totally untested and probably broken code below, but should demonstrate the idea:
-(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];
}
// Now that we know myTimer doesn't point to a timer already..
myTimer = [NSTimer scheduledTimerWithTimeInterval:aTimeInterval target:self selector:@selector(echoIt:) userInfo:myDict repeats:YES];
[myTimer retain];
}
-(IBAction)cancelIt:(id) sender {
[myTimer invalidate];
[myTimer release]; // This timer is now gone, and you won't reuse it.
}
So, my goal is to use 1 start button and 1 cancel button.. and just do their actions. I have set up a the start button to start both timers, obviously both start their countdown at the same time which is not good.
I want to tell one timer to start and if I press cancel, invalidate it. Then If I press start again, call the second timer. (I do this because I read that you can't reuse a timer after you invalidate it).
Some people have suggested to use Booleans like true or false, or conditions. What do you think?
What if after pressing the start button, you create a timer and start it. Then pressing the cancel button invalidates and releases it. Then pressing the start button would create another timer, using the same pointer.
Totally untested and probably broken code below, but should demonstrate the idea:
-(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];
}
// Now that we know myTimer doesn't point to a timer already..
myTimer = [NSTimer scheduledTimerWithTimeInterval:aTimeInterval target:self selector:@selector(echoIt:) userInfo:myDict repeats:YES];
[myTimer retain];
}
-(IBAction)cancelIt:(id) sender {
[myTimer invalidate];
[myTimer release]; // This timer is now gone, and you won't reuse it.
}
more...
jake4ever
Apr 5, 10:00 PM
4.2.6 required!? But I hate to update.. :(
malim
Apr 15, 07:49 PM
I personally will not rule out that this image is 100% fake. Inspecting the image closely reveal that there are a dust speck. Dust speck exist on the camera lens or sensor and the photos does have that. Another thing is if the camera lens dirty because of probably moist it will have those specks.
I am sure based on other rumors that Apple already booked the place for special event this June might also can be relate to this.
If the next generation of iPhone or iPod shell are made from aluminium it is possible. Everything about technology is possible. So nothing impossible to have an aluminium casing if someone said that it will interfere with the signal as lots of component inside the current devices consist of many sorts of metal.
But I thought that a bit curvature at the surface would look better.
http://www.macrumors.com/images/macrumorsthreadlogo.gif (http://www.macrumors.com/2010/04/15/questionable-next-generation-iphone-rear-shell-images-surface/)
http://images.macrumors.com/article/2010/04/15/130851-iphone_shell_1_500.jpg
We have received a set of images purportedly depicting an iPad-inspired rear shell design for the next-generation iPhone. While we have questions about the validity of the images given their claimed origins and other issues, they are interesting enough that we have decided to publish them here on Page 2 for discussion purposes.
http://images.macrumors.com/article/2010/04/15/130851-iphone_shell_2_500.jpg
Text on the back of the claimed shell indicate that it is a 64 GB model, and the first line of small text includes Apple's traditional "Designed by Apple in California Assembled in China" information. Unfortunately, the images are not of high enough quality to interpret the second line of text, which would contain the model number and FCC and IC ID numbers.
http://images.macrumors.com/article/2010/04/15/130851-iphone_shell_3_500.jpg
The images also show cutouts for the same physical features found on existing iPhone models, with a circular camera lens hole at the top left of the rear shell, space for a ring/silent switch and volume rocker along the side, and dock connector, microphone, speaker, and a pair of screw holes along the bottom.
Metadata included with the images indicates that they have passed through Photoshop CS4, with the first two images carrying yesterday's date while the third carries a date of March 23rd.
Article Link: Questionable Next-Generation iPhone Rear Shell Images Surface (http://www.macrumors.com/2010/04/15/questionable-next-generation-iphone-rear-shell-images-surface/)
I am sure based on other rumors that Apple already booked the place for special event this June might also can be relate to this.
If the next generation of iPhone or iPod shell are made from aluminium it is possible. Everything about technology is possible. So nothing impossible to have an aluminium casing if someone said that it will interfere with the signal as lots of component inside the current devices consist of many sorts of metal.
But I thought that a bit curvature at the surface would look better.
http://www.macrumors.com/images/macrumorsthreadlogo.gif (http://www.macrumors.com/2010/04/15/questionable-next-generation-iphone-rear-shell-images-surface/)
http://images.macrumors.com/article/2010/04/15/130851-iphone_shell_1_500.jpg
We have received a set of images purportedly depicting an iPad-inspired rear shell design for the next-generation iPhone. While we have questions about the validity of the images given their claimed origins and other issues, they are interesting enough that we have decided to publish them here on Page 2 for discussion purposes.
http://images.macrumors.com/article/2010/04/15/130851-iphone_shell_2_500.jpg
Text on the back of the claimed shell indicate that it is a 64 GB model, and the first line of small text includes Apple's traditional "Designed by Apple in California Assembled in China" information. Unfortunately, the images are not of high enough quality to interpret the second line of text, which would contain the model number and FCC and IC ID numbers.
http://images.macrumors.com/article/2010/04/15/130851-iphone_shell_3_500.jpg
The images also show cutouts for the same physical features found on existing iPhone models, with a circular camera lens hole at the top left of the rear shell, space for a ring/silent switch and volume rocker along the side, and dock connector, microphone, speaker, and a pair of screw holes along the bottom.
Metadata included with the images indicates that they have passed through Photoshop CS4, with the first two images carrying yesterday's date while the third carries a date of March 23rd.
Article Link: Questionable Next-Generation iPhone Rear Shell Images Surface (http://www.macrumors.com/2010/04/15/questionable-next-generation-iphone-rear-shell-images-surface/)
more...
COSWORTH
Mar 17, 09:01 AM
what exactly is this Karma everyone speaks of? Who brings down the karma, good or bad? Is there a Karma Fairy? Karma Bunny? Karma Leprechaun?
suneohair
Mar 28, 02:03 PM
http://tallahassee.craigslist.org/search/sss?query=xbox%20360
Can you give me some details about the games? Maybe one title name and the number stolen.
Can you give me some details about the games? Maybe one title name and the number stolen.
more...
MacSedgley
Aug 8, 01:05 PM
I managed scrape together enough money together for a 20 incher and a mini last year (�1000). They gave me the wrong box (a 23") which was the nicest thing thats ever happened to me.
Its a lovely screen, but the colours are all over the place (and people should be very wary when using front row with the macbook linked to a cinema - for some reason it doesnt go to sleep, and this could lead to some nasty screen burn.)
A decent screen is a big investment - you would expect a good LCD to last you at least 5 years if your paying a grand for it. At the moment, Dell's is much better value in my book, even though it is hideously ugly.
Anyone tried the new NECs?
Its a lovely screen, but the colours are all over the place (and people should be very wary when using front row with the macbook linked to a cinema - for some reason it doesnt go to sleep, and this could lead to some nasty screen burn.)
A decent screen is a big investment - you would expect a good LCD to last you at least 5 years if your paying a grand for it. At the moment, Dell's is much better value in my book, even though it is hideously ugly.
Anyone tried the new NECs?
Eolian
Mar 24, 06:24 PM
One of my favorite old Zepplin tunes :) I think I've kept all my install CDs from 10.1 on; wow, time has been marchin' along :D
Good on ya Apple :apple:
Good on ya Apple :apple:
more...
holmesf
Apr 30, 10:19 PM
You are talking about things that would happen if they closed it today. I said 15 years. :)
And it's not a doomsday proposition or anything. That's just where the entire industry will go.
15 years from now? By then the tech world will be so unrecognizable we might as well not debate it. 15 years ago I was using a Mac LC, all my software came from the local mac reseller on floppy disk, and I was just beginning to hear about this whole "Internet" thing. I don't think anybody at the time imagined things turning out quite as they did. Even predicting things 5 years down the line is pretty damned hard in the tech world.
Which is to say, you may very well be right when we talk about 15 years from now. On the other hand, perhaps 15 years from now the whole notion of an app store will seem like a quaint remnant of the past.
And it's not a doomsday proposition or anything. That's just where the entire industry will go.
15 years from now? By then the tech world will be so unrecognizable we might as well not debate it. 15 years ago I was using a Mac LC, all my software came from the local mac reseller on floppy disk, and I was just beginning to hear about this whole "Internet" thing. I don't think anybody at the time imagined things turning out quite as they did. Even predicting things 5 years down the line is pretty damned hard in the tech world.
Which is to say, you may very well be right when we talk about 15 years from now. On the other hand, perhaps 15 years from now the whole notion of an app store will seem like a quaint remnant of the past.
lordonuthin
Apr 27, 09:34 PM
heck, you know there's a motherboard out there that can hold 2 x i7 980x for $600 i think. now that would be awesome - but just 2 processors and motherboard would cost over $2600
I thought about that, getting one cpu now and getting another one down the road, but the board was only $200 (http://www.newegg.com/Product/Product.aspx?Item=N82E16813128423) in this case maybe 2 systems would be better than one - if I get another one down the road or if Apple EVER gets around to making a new Mac Pro :rolleyes:
I thought about that, getting one cpu now and getting another one down the road, but the board was only $200 (http://www.newegg.com/Product/Product.aspx?Item=N82E16813128423) in this case maybe 2 systems would be better than one - if I get another one down the road or if Apple EVER gets around to making a new Mac Pro :rolleyes:
more...
ipedro
Sep 25, 11:29 AM
I suppose there could be a bit of news here for non-photographers.
As I understand it, Aperture uses OS X's built-in RAW image processing. If I remember rightly, the last Aperture update accompanied an OS X update. So it's possible 10.4.8 could be just around the corner (i.e. sometime this week?)
It's a Photography show .... It baffles my mind that people make far out unfounded predictions and then are disappointed and curse Apple when they don't come true.
The best example of that was the "One More Thing" event where the iPod Hi-Fi and Intel Mac Mini were shown. This event wasn't meant for the general public, so much that it wasn't broadcast to the public.
Now here's another example which Apple doesn't hype about to the public and "darn, all they do is show an update to a photography pro tool at a photography convention... Apple stock will surely fall with this news"
I for one am real happy with the offline feature. I've been using a workaround to save my giant library off my MacBook Pro. The iLife connectivity and Flickr plugin are also very welcome.
Now I'm just hoping that this version of Aperture is a little snappier because even on a fully loaded MBP, I get beachballs all the time.
As I understand it, Aperture uses OS X's built-in RAW image processing. If I remember rightly, the last Aperture update accompanied an OS X update. So it's possible 10.4.8 could be just around the corner (i.e. sometime this week?)
It's a Photography show .... It baffles my mind that people make far out unfounded predictions and then are disappointed and curse Apple when they don't come true.
The best example of that was the "One More Thing" event where the iPod Hi-Fi and Intel Mac Mini were shown. This event wasn't meant for the general public, so much that it wasn't broadcast to the public.
Now here's another example which Apple doesn't hype about to the public and "darn, all they do is show an update to a photography pro tool at a photography convention... Apple stock will surely fall with this news"
I for one am real happy with the offline feature. I've been using a workaround to save my giant library off my MacBook Pro. The iLife connectivity and Flickr plugin are also very welcome.
Now I'm just hoping that this version of Aperture is a little snappier because even on a fully loaded MBP, I get beachballs all the time.
alexbates
Oct 6, 08:06 PM
That has to be the best Verizon commercial ever! :D I am now really convinced that I should switch from AT&T.
Savor
Mar 17, 07:10 PM
I don't have the same story or friends like you do, so no. In Los Angeles/Orange County, Apple Stores are abundant and within a 20 miles from each other it seems. I do have some people glance at my phone from time to time especially when I am at MetroPCS paying my dad's phone bill. LOL. I don't really care for the attention and keep it incognito most of the time next to my waist.
But your story doesn't surprise especially if you can come from the UK. iPhone did slip out of the TOP 5 in sales last year. I believe the HTC Desire was the most popular one. One of my favorite reviewers from the UK is James Whatley. He reminds me of Brandon Flowers from The Killers. He despises Apple with a passion. He works for Nokia now, so call him one of those diehard Nokians.
I think most of the hatred isn't at the iPhone at all but at Apple. No different than hating the Lakers or Yankees. It is too damn popular and people just end up getting sick of it altogether. Not everybody wants to follow the iSheep. People yearn for their own individuality and don't always want something everybody and their grandma has. Think different, remember? In a few years, people will get sick of Android and WP7 too once they start to decline in popularity. All cycles. There was a time when people laughed at Nintendo and are now hip for the casual masses. Every company has their ups and downs. I see the cell phone market similar to the video game market. You build a platform and try to see to sell it fast to attract software developers. Eventually, it declines and you either rest on your laurels for it to become played out or you take the next jump and hope it doesn't alienate your core audience. Sometimes it does just like it does for many popular rock bands. They change it up too much with their music that people can't accept the change anymore. Or you rest on your laurels and become what Nokia and RIM have been the last couple years.
By 2020, who knows if any of them will still exist or be the most popular OS out there? Every product line can die out eventually. And if they did still exist, it won't be how we see them now.
But your story doesn't surprise especially if you can come from the UK. iPhone did slip out of the TOP 5 in sales last year. I believe the HTC Desire was the most popular one. One of my favorite reviewers from the UK is James Whatley. He reminds me of Brandon Flowers from The Killers. He despises Apple with a passion. He works for Nokia now, so call him one of those diehard Nokians.
I think most of the hatred isn't at the iPhone at all but at Apple. No different than hating the Lakers or Yankees. It is too damn popular and people just end up getting sick of it altogether. Not everybody wants to follow the iSheep. People yearn for their own individuality and don't always want something everybody and their grandma has. Think different, remember? In a few years, people will get sick of Android and WP7 too once they start to decline in popularity. All cycles. There was a time when people laughed at Nintendo and are now hip for the casual masses. Every company has their ups and downs. I see the cell phone market similar to the video game market. You build a platform and try to see to sell it fast to attract software developers. Eventually, it declines and you either rest on your laurels for it to become played out or you take the next jump and hope it doesn't alienate your core audience. Sometimes it does just like it does for many popular rock bands. They change it up too much with their music that people can't accept the change anymore. Or you rest on your laurels and become what Nokia and RIM have been the last couple years.
By 2020, who knows if any of them will still exist or be the most popular OS out there? Every product line can die out eventually. And if they did still exist, it won't be how we see them now.
twoodcc
Apr 13, 06:13 PM
Oh yeah thanks to your help in getting the SMP client and giving the GPU client a go, I am now in the top 20 producers. Not bad considering when a few years back I had only an iBook and I was producing 48 points a day and did that for over a year!
I don't know how long I will be able to sustain that rate though might have to drop back.
yeah no problem.
well just put up those numbers for as long as you can. our team can use the points, and of course for the cause
I don't know how long I will be able to sustain that rate though might have to drop back.
yeah no problem.
well just put up those numbers for as long as you can. our team can use the points, and of course for the cause
wlh99
Apr 27, 11:34 AM
I see where you going wlh99, and don't worry.. my full intention is to learn, not to get code from all of you. Many people in this thread underestimate my knowledge of objective C (and I understand why, I got lost with the pointers). I have 2 1/2 months since I started development and had 0 idea of the language or programming (I was a Pastry Chef actually :D, which is the name of my first app).
Believe me when I tell you that I know what's going on with my code. I'm aware that If you release an object that it doesn't exist you'll get an exception every time.
Making it work is a lot less important than knowing how to do it, for future work.
Back to the Code, let me go give it try.. b-back
UPDATE**
Ok, it doesn't crash now but timer still won't restart. I'm going to create another timer object (not pointer, I'll use the same pointer). I get this idea that I can't reuse or reset the same timer over again (invalidating and releasing it only pauses the timer). Wish me luck :)
Good luck.
Post your echoIt: method. If you are displaying elapsed seconds or something, the code to calculate and display that might be your issue.
Believe me when I tell you that I know what's going on with my code. I'm aware that If you release an object that it doesn't exist you'll get an exception every time.
Making it work is a lot less important than knowing how to do it, for future work.
Back to the Code, let me go give it try.. b-back
UPDATE**
Ok, it doesn't crash now but timer still won't restart. I'm going to create another timer object (not pointer, I'll use the same pointer). I get this idea that I can't reuse or reset the same timer over again (invalidating and releasing it only pauses the timer). Wish me luck :)
Good luck.
Post your echoIt: method. If you are displaying elapsed seconds or something, the code to calculate and display that might be your issue.
p0intblank
Oct 19, 10:24 AM
Movin' on up!!! :D
squirrellydw
Apr 16, 02:58 PM
1. Was the iPhone the first smart phone = No
2. Is the iPhone best smart phone = yes and no, depends on what you like and your needs.
3. Did it change the cell phone industry = Yes, are the experts agree. Apple simply did what they always have done. They improve on a product that has already been established in most cases.
The Apple ecosystem is no more open or closed then any other system, Apple, Android, Rim, Windows etc.
If I want to do certain things with an iPhone I have to jailbreak it, same with Android it's just called rooting.
end of story, move on
2. Is the iPhone best smart phone = yes and no, depends on what you like and your needs.
3. Did it change the cell phone industry = Yes, are the experts agree. Apple simply did what they always have done. They improve on a product that has already been established in most cases.
The Apple ecosystem is no more open or closed then any other system, Apple, Android, Rim, Windows etc.
If I want to do certain things with an iPhone I have to jailbreak it, same with Android it's just called rooting.
end of story, move on
Mitthrawnuruodo
Aug 1, 10:41 AM
How can a Norwegian law affect Denmark like this?:confused:Gjennom EØS (http://en.wikipedia.org/wiki/European_Economic_Area)-avtalen... :(
