lmalave
Oct 19, 11:39 AM
Two can play at that game. I still have the 400 shares I bought in 1997.
Do the math. :)
Split twice so that's 1600 shares now. $125K - you got him beat ;)
Do the math. :)
Split twice so that's 1600 shares now. $125K - you got him beat ;)
chrisgeleven
Jan 5, 03:23 PM
Why did Apple do away with live feeds of the event? That seems like a good idea. What are they trying to avoid?
That little thing called bandwidth. You know how many people will be hitting that streaming video stream if it were live? With it being tape delayed, Apple can somewhat spread out the number of people who will be watching it.
Heck I have a hard enough time viewing the keynote hours after it was released, never mind trying to do it live.
That little thing called bandwidth. You know how many people will be hitting that streaming video stream if it were live? With it being tape delayed, Apple can somewhat spread out the number of people who will be watching it.
Heck I have a hard enough time viewing the keynote hours after it was released, never mind trying to do it live.
KnightWRX
Apr 28, 04:27 AM
Look, your attitude really needs some adjustment Nekbeth. I have not asked a single trick question. My questions have all been about trying to understand what it is you're trying to do and what problems you are facing. You have been less than clear this whole time.
I think part of that problem is that you're thinking "I'm a newbie, these guys are pros, I'll probably get help but end up being laughed at". Seriously, if I want to laugh at people, I'll just head over to the news discussion. Those guys are a riot. And I'm not a pro at all. Sure I've been doing this for 15 some odd years in one form or another, but never as a job, only as a hobby.
The programming forum is full of newbies. I was a newbie once too. We all start somewhere and it's no laughing matter. I wouldn't spend all this time trying to figure out what it is you're doing wrong if it was only to laugh at you in the end.
Relax and try to realise we want to help you, otherwise we wouldn't be posting here. Now listen to us. We need your help too. As Pros, there are things we know that you might not, and you need to be clear and specific about your problem and what you're not understanding.
Now I'll try to take a look at the code you posted (I just got up and I need to get to work) and see if I can dig out something if someone doesn't do it faster than me.
I think part of that problem is that you're thinking "I'm a newbie, these guys are pros, I'll probably get help but end up being laughed at". Seriously, if I want to laugh at people, I'll just head over to the news discussion. Those guys are a riot. And I'm not a pro at all. Sure I've been doing this for 15 some odd years in one form or another, but never as a job, only as a hobby.
The programming forum is full of newbies. I was a newbie once too. We all start somewhere and it's no laughing matter. I wouldn't spend all this time trying to figure out what it is you're doing wrong if it was only to laugh at you in the end.
Relax and try to realise we want to help you, otherwise we wouldn't be posting here. Now listen to us. We need your help too. As Pros, there are things we know that you might not, and you need to be clear and specific about your problem and what you're not understanding.
Now I'll try to take a look at the code you posted (I just got up and I need to get to work) and see if I can dig out something if someone doesn't do it faster than me.
Broojo02
May 2, 09:23 AM
Kinda glad about this, the new sliders did look awesome and very iOSy but the slight delay in seeing a switch between two different states with the animation, especially between two areas far away could be a bit annoying and time consuming. We are only talking like 1/2 a second max probably but that is still something compared to the instant response of having a simple button.
payup
Jul 21, 10:33 PM
At 0:42 he changes his grip to hold the phone to holding it with just his fingers and the signal rises again. It looks like his fingertips are touching the lower left of the phone. If you do this on the iPhone 4 and bridge the antenna gap, you don't regain signal.
Looks to me like they're trying to pass off the problem of bridging the antenna gap on the iPhone as the same as blocking the antenna with your whole hand on all phones. All phones have the latter problem... But that's not the issue here.
This is exactly what they're doing. All phones will drop bars if held certain way yes. But there's no phones that will drop a call if touched with a single finger in a certain spot. I love everything else about the phone, but phone part of it is impossible to use, I dropped at least 10 calls today!
Looks to me like they're trying to pass off the problem of bridging the antenna gap on the iPhone as the same as blocking the antenna with your whole hand on all phones. All phones have the latter problem... But that's not the issue here.
This is exactly what they're doing. All phones will drop bars if held certain way yes. But there's no phones that will drop a call if touched with a single finger in a certain spot. I love everything else about the phone, but phone part of it is impossible to use, I dropped at least 10 calls today!
tny
Oct 29, 11:10 AM
huh??
Yes, what he is saying about "Free" software is true. "Free" software is about what rights to use the source code the user has; most "Free" software is available in at least some commercial version for a fee (e.g., Red Hat Linux, MySQL).
Yes, what he is saying about "Free" software is true. "Free" software is about what rights to use the source code the user has; most "Free" software is available in at least some commercial version for a fee (e.g., Red Hat Linux, MySQL).
dunk321
Mar 17, 01:12 AM
Haaaaaaa just shared a launch day story, and the majority of you would have hauled ass with iPad in hand for the price I paid. Haters lmfao
andyblac
Aug 9, 11:58 AM
UK specs have been updated.
:), just ordered myself a Mac Pro 2.66 with 20" ACD. shipping on the 15th August :D
:), just ordered myself a Mac Pro 2.66 with 20" ACD. shipping on the 15th August :D
leekohler
May 5, 05:49 PM
I guess it's a good thing that I've given up hope that America will give up it's gun obsession.
Since as you say, there are no possible solutions. :rolleyes:
Look at the "drug war". Do you really want a "gun war"? Really?
The answer with things like this, as always, lies in regulation and education- not bans. We can minimize the problem, but it will never go away.
Since as you say, there are no possible solutions. :rolleyes:
Look at the "drug war". Do you really want a "gun war"? Really?
The answer with things like this, as always, lies in regulation and education- not bans. We can minimize the problem, but it will never go away.
CasaRed
Jul 27, 03:36 PM
I agree that as priced that the majority of people getting this car would lease it. Keep in mind though that if you have a daily commute of less than 40 miles, you'll seldom need to purchase gasoline, so compared to a regular car or even a Prius, those savings will add up faster.
Either way, at this point this car seems to be at an early-adopter stage where you would expect to be paying a premium until it becomes more of a commodity or there's more competitors in the space. Kinda like how a 5gb iPod used to cost $400. ;)
Either way, at this point this car seems to be at an early-adopter stage where you would expect to be paying a premium until it becomes more of a commodity or there's more competitors in the space. Kinda like how a 5gb iPod used to cost $400. ;)
twoodcc
May 12, 06:40 PM
your very dedicated ;)
have you set up any sort of remote capabilities? so you can remote into each system etc just incase there is something wrong - or to check up on heat?
what are you guy's rigs!?
haha thanks. i try to be.
i thought about doing this, and it wouldn't be very hard to do, but if something goes wrong, there's really nothing i can do remotely. the only things that seem to go wrong is the computer crashing, or restarting. either way, i don't have auto login, so i wouldn't be able to get to it remotely. heat isn't the problem right now (it was when i was trying 4.0 ghz - or 4 x gpu).
my main 3 rigs (i need names!)
1. Asus - running 3.5 ghz i7 920. 2 x GTX 260
2. Alienware - 3.6 ghz i7 920 now. 2 x GTX 260
3. home built (need name) - 3.6 ghz i7 930 now. 1 x GTX 260, 1 x GTS 250.
and i've got my ps3 folding and my macbook pro gpu folding right now, but not all the time
have you set up any sort of remote capabilities? so you can remote into each system etc just incase there is something wrong - or to check up on heat?
what are you guy's rigs!?
haha thanks. i try to be.
i thought about doing this, and it wouldn't be very hard to do, but if something goes wrong, there's really nothing i can do remotely. the only things that seem to go wrong is the computer crashing, or restarting. either way, i don't have auto login, so i wouldn't be able to get to it remotely. heat isn't the problem right now (it was when i was trying 4.0 ghz - or 4 x gpu).
my main 3 rigs (i need names!)
1. Asus - running 3.5 ghz i7 920. 2 x GTX 260
2. Alienware - 3.6 ghz i7 920 now. 2 x GTX 260
3. home built (need name) - 3.6 ghz i7 930 now. 1 x GTX 260, 1 x GTS 250.
and i've got my ps3 folding and my macbook pro gpu folding right now, but not all the time
SBlue1
May 4, 03:32 AM
I'll buy one when it gets a capacitive pressure based screen/stylus (Like the HTC Flyer)
Ill buy one when it gets multiple user accounts.
Ill buy one when it gets multiple user accounts.
KnightWRX
Apr 28, 09:42 AM
So, please don't take everything I typed and generalize it, because it's not for everyone.
I do understand where Dejo, Balamw and the others are coming from though. And frankly, they are probably better suited to help you than I am. I don't have a lot of experience with Objective-C and Cocoa, not like they do, having mostly come into it recently.
Back to the code, here is a photo of my connections (ignore canceBigtimer). What you say is true I don't know how NSTimer works entirely , just some parts, I realize that and it is one of the reason I postpone my timer for a future update (need to study it).
I have two timers, because, like I said.. I don't have full knowledge of timers. I know now that 1 timer is enough, even if I use two timers and start them at the same time, the log only shows 1 loop and the countdown in separate labels show e.g. 59 in one and 58 in another and so on.
Ok, how about we work on making 1 timer work then ? The code you posted is very complicated and I don't think it has to be this complicated. Going 1 timer would simplify this.
I see your Start Button is associated to 3 actions. Is this really what you want ? Let's simplify this. As an exercise, make 1 method, call it startTimer (like I did) and have only that action associated with your start button. From there, you can call the other methods yourself as needed.
Once you have modified the code in this way, post again what you have in full, what it is doing and what you think it should be doing. We'll go from there.
You mention my two global variables, It makes sense that the timer does not stop because the variables are outside the method that creates the timer. is that whats going on?
No, the variables are "fine" where they are. They would be better positionned in the @interface block and declared as instance variables, but implementation scope globals work too.
What you need to do however is reset those if you want your timer to start back at 0. Somewhere in your "stop/reset" code, there needs to be an initialization of those back to 0 :
seconds = 0;
minutes = 0;
If your Cancel button is what should reset it, then this should be right now in newActionTimer. But ideally, we'll get rid of that function when you simplify the code down to 1 timer.
Look at my NSLog outputs in my screenshot earlier. There's 3 methods there. updateLabel, cancelTimer, startTimer. This should have given you a big indication of how not complicated you should have made this.
If you want 3 buttons, start, reset, stop, you'd technically need 4 methods, as follows :
-(IBAction) startTimer: (id) sender;
-(IBAction) stopTimer: (id) sender;
-(IBAction) resetTimer: (id) sender;
-(void) updateLabel;
One to update the label as needed, one to start the timer, one to stop it and one to reset it.
Also, NSTimer is not your timer. The timer is what you are creating with ATimerViewController. You need to grasp this. NSTimer simply calls methods, in this case, it should be update label. That's about all it should be doing. Both the stop and reset methods should release the NSTimer object instance. startTimer should always create a new one. However, reset should be the one to set back seconds/minutes to 0.
I do understand where Dejo, Balamw and the others are coming from though. And frankly, they are probably better suited to help you than I am. I don't have a lot of experience with Objective-C and Cocoa, not like they do, having mostly come into it recently.
Back to the code, here is a photo of my connections (ignore canceBigtimer). What you say is true I don't know how NSTimer works entirely , just some parts, I realize that and it is one of the reason I postpone my timer for a future update (need to study it).
I have two timers, because, like I said.. I don't have full knowledge of timers. I know now that 1 timer is enough, even if I use two timers and start them at the same time, the log only shows 1 loop and the countdown in separate labels show e.g. 59 in one and 58 in another and so on.
Ok, how about we work on making 1 timer work then ? The code you posted is very complicated and I don't think it has to be this complicated. Going 1 timer would simplify this.
I see your Start Button is associated to 3 actions. Is this really what you want ? Let's simplify this. As an exercise, make 1 method, call it startTimer (like I did) and have only that action associated with your start button. From there, you can call the other methods yourself as needed.
Once you have modified the code in this way, post again what you have in full, what it is doing and what you think it should be doing. We'll go from there.
You mention my two global variables, It makes sense that the timer does not stop because the variables are outside the method that creates the timer. is that whats going on?
No, the variables are "fine" where they are. They would be better positionned in the @interface block and declared as instance variables, but implementation scope globals work too.
What you need to do however is reset those if you want your timer to start back at 0. Somewhere in your "stop/reset" code, there needs to be an initialization of those back to 0 :
seconds = 0;
minutes = 0;
If your Cancel button is what should reset it, then this should be right now in newActionTimer. But ideally, we'll get rid of that function when you simplify the code down to 1 timer.
Look at my NSLog outputs in my screenshot earlier. There's 3 methods there. updateLabel, cancelTimer, startTimer. This should have given you a big indication of how not complicated you should have made this.
If you want 3 buttons, start, reset, stop, you'd technically need 4 methods, as follows :
-(IBAction) startTimer: (id) sender;
-(IBAction) stopTimer: (id) sender;
-(IBAction) resetTimer: (id) sender;
-(void) updateLabel;
One to update the label as needed, one to start the timer, one to stop it and one to reset it.
Also, NSTimer is not your timer. The timer is what you are creating with ATimerViewController. You need to grasp this. NSTimer simply calls methods, in this case, it should be update label. That's about all it should be doing. Both the stop and reset methods should release the NSTimer object instance. startTimer should always create a new one. However, reset should be the one to set back seconds/minutes to 0.
gootz
Aug 15, 12:43 AM
I went into my local Apple store yesterday and they denied that there were even upgrades? WTF? I guess they want to sell off there current stock?
KingCrimson
Apr 21, 08:00 PM
Hopefully it's totally new from the ground up, ditch all the Win32/legacy crap that's hindered MSFT for years.
Jetson
Oct 12, 10:15 AM
The reason I posted my concern about the scratches on the 5G iPod is because I'm a longtime Apple customer. I was one of the first to buy the iPod when it came to market. I love Apple products.
However, Apple has responded to this scratch issue very poorly. Apple won't even acknowledge that there is a problem, blaming scratches on customer abuse.
Well when you start blaming the customers, then you are definitely on the wrong road. Customers who are not enamored of Apple (don't own a Mac) will switch to the Zune. If you can't understand the basics of how the market operates, then I can see why you are taking potshots.
SavMan hasn't provided any reference or link to support his claim, true or not, physics or not. His claims are anecdotal. Second, whatever the cause of the proliferation of scratches which have generated many, many complaints, denying that scratches exist is foolish, indeed stupid.
If Apple wants to keep its iPod cash cow, I sincerely hope that they address the scratch issue. There is serious competition on the horizon (Zune) and you can't take the customer for granted anymore.
However, Apple has responded to this scratch issue very poorly. Apple won't even acknowledge that there is a problem, blaming scratches on customer abuse.
Well when you start blaming the customers, then you are definitely on the wrong road. Customers who are not enamored of Apple (don't own a Mac) will switch to the Zune. If you can't understand the basics of how the market operates, then I can see why you are taking potshots.
SavMan hasn't provided any reference or link to support his claim, true or not, physics or not. His claims are anecdotal. Second, whatever the cause of the proliferation of scratches which have generated many, many complaints, denying that scratches exist is foolish, indeed stupid.
If Apple wants to keep its iPod cash cow, I sincerely hope that they address the scratch issue. There is serious competition on the horizon (Zune) and you can't take the customer for granted anymore.
KnightWRX
Mar 13, 09:59 AM
Tablets don't even redefine computing at all anyway. It's all the same it's always been. A device that takes input, processes it according to a set of instructions, and outputs a result or provides storage.
That's the basic definition of a computer. iPad, iPhone, Macbook, Xserve, Mac Pro, they are all computers. You use them to input data, process it, store it or output it to an output device (printer, screen).
To think there's some kind of paradigm-shift going is simply having your head in the clouds.
For programmers, nothing has changed, we're doing the same thing with the devices people in the 1970s were doing, albeit, with more refined output capabilities and different input devices.
For server admins nothing has changed. These thin/fat clients are still needing server architectures to drive them and still use the very core Client/Server model for most of their servers. Heck, moving things "into the cloud", just means more power on the server backend and less in the client. That means more infrastructure to manage for us server guys. :D "Cloud computer" is just another way of saying "Client/Server" model and the 60s called about that, they want us to quit renaming their concept.
For "desktop support" people, nothing has changed. Devices have to be imaged with the software the customer needs, it needs to be configured and that configuration needs to be managed. It needs to get hardware service when broken. It needs software support for when things don't really work right or for when the user needs a live person "manual" to reference.
Heck, I'd go so far as to argue even for users, what really changed ? iPad is a big e-mail, web, facebook, gaming device. PCs/Laptops have been this for these people for the last 10 or 15 years. They are doing the same thing on tablets that they were on laptops. There's no paradigm shift at all, just a different format. It would be like calling laptops a paradigm shift when they came out.
That's the basic definition of a computer. iPad, iPhone, Macbook, Xserve, Mac Pro, they are all computers. You use them to input data, process it, store it or output it to an output device (printer, screen).
To think there's some kind of paradigm-shift going is simply having your head in the clouds.
For programmers, nothing has changed, we're doing the same thing with the devices people in the 1970s were doing, albeit, with more refined output capabilities and different input devices.
For server admins nothing has changed. These thin/fat clients are still needing server architectures to drive them and still use the very core Client/Server model for most of their servers. Heck, moving things "into the cloud", just means more power on the server backend and less in the client. That means more infrastructure to manage for us server guys. :D "Cloud computer" is just another way of saying "Client/Server" model and the 60s called about that, they want us to quit renaming their concept.
For "desktop support" people, nothing has changed. Devices have to be imaged with the software the customer needs, it needs to be configured and that configuration needs to be managed. It needs to get hardware service when broken. It needs software support for when things don't really work right or for when the user needs a live person "manual" to reference.
Heck, I'd go so far as to argue even for users, what really changed ? iPad is a big e-mail, web, facebook, gaming device. PCs/Laptops have been this for these people for the last 10 or 15 years. They are doing the same thing on tablets that they were on laptops. There's no paradigm shift at all, just a different format. It would be like calling laptops a paradigm shift when they came out.
arkitect
Apr 21, 11:25 AM
Ha!
So someone voted my post -1 and I managed to bump it back to 0�
Of course I am quite sure it'll be back to -10 soon. :D
So someone voted my post -1 and I managed to bump it back to 0�
Of course I am quite sure it'll be back to -10 soon. :D
peharri
Oct 31, 09:34 AM
The thin veneer is off the vast majority of people that clamor for OSS.
Whenever I hear the OSS crowd scream "Software should be FREE!" I translate that to mean "I refuse to pay someone for their work, thus I will STEAL it"!
I don't blame Apple. The OSS community abused what they had and turned to piracy by stealing the GUI. Kudos Apple.
What on Earth are you talking about? What are people stealing in the Arn's summary? The modified code isn't capable of running OS X, and until they closed the source, Darwin worked on most generic x86 platforms anyway.
Someone fixes a lack of functionality that existed in previous public versions and you call it "stealing"? WTF?
Whenever I hear the OSS crowd scream "Software should be FREE!" I translate that to mean "I refuse to pay someone for their work, thus I will STEAL it"!
I don't blame Apple. The OSS community abused what they had and turned to piracy by stealing the GUI. Kudos Apple.
What on Earth are you talking about? What are people stealing in the Arn's summary? The modified code isn't capable of running OS X, and until they closed the source, Darwin worked on most generic x86 platforms anyway.
Someone fixes a lack of functionality that existed in previous public versions and you call it "stealing"? WTF?
tophergt
Oct 19, 10:09 AM
Do you believe that the perpetual delay of Microsoft's Vista OS is allowing Apple to temporarily grab up some of the markey share? I'm not saying that people who would otherwise purchase a Wintel machine are switching to Mac because Vista is not out, but rather that some percentage are waiting to buy their new Core2Duo machine (or other upgrade to their current box) until they can get an full release version of Vista preinstalled on it.
Just a conjecture, but I thought it was worth considering. I suppose we'll find out in the first two quarters of 2007 when Microsoft decides that they're ready to release that bad boy on the world . . .
[JDOG, your post came in while I was still typing mine . . . sorry for the repeat]
Just a conjecture, but I thought it was worth considering. I suppose we'll find out in the first two quarters of 2007 when Microsoft decides that they're ready to release that bad boy on the world . . .
[JDOG, your post came in while I was still typing mine . . . sorry for the repeat]
geocom
Jan 11, 11:53 PM
I would not see a problem with them going to report at macworld if anything happens in the keynote Steve would recover like he did at last years Mac World where his clicker stopped working and you are also talking about a mac event unlike CES things don't crash :)
mochacian
Apr 5, 09:10 PM
I have to say, this is the dumbest idea I've ever seen come out of Cupertino. Even worse than the Newton.
I feel sorry for the tools who download this.
I'm one if the "tools" that downloaded it. I appreciate you feeling sorry for me but I don't need it if I'm downloading apps from an iOS device. I need it if I'm in Japan or anyone of the people affected by tragedy ruining there life. Please feel sorry for them and maybe donate $5 to the relief efforts.
I feel sorry for the tools who download this.
I'm one if the "tools" that downloaded it. I appreciate you feeling sorry for me but I don't need it if I'm downloading apps from an iOS device. I need it if I'm in Japan or anyone of the people affected by tragedy ruining there life. Please feel sorry for them and maybe donate $5 to the relief efforts.
saving107
May 2, 09:46 AM
We've been sent the OS and while we haven't loaded it on our iPhone just yet, here is what we have been told it will address:
- Battery life improvements.
Well this should make some people very happy (but will it finally, once and for all, fix the battery life of the iPhone?)
- Battery life improvements.
Well this should make some people very happy (but will it finally, once and for all, fix the battery life of the iPhone?)
ConnorCG
Apr 29, 01:11 PM
The power of Mac OS X. The magic of iPad.
Oh god...
Oh god...
No comments:
Post a Comment