Atom feedLast 5 comments
37 years ago
Ray: Having the same problem. Very frustrating. Luckily, for some reason my released version worked on the iPad itself, but now I can't get it to run in the simulator. Getting no such table, which I'm guessing is an initialization error. Will continue to investigate.
Ray: Having the same problem. Very frustrating. Luckily, for some reason my released version worked on the iPad itself, but now I can't get it to run in the simulator. Getting no such table, which I'm guessing is an initialization error. Will continue to investigate.
38 years ago
Jeremy: FYI, I've just tried it with the SQLite 3.7.0 preview and the same problem occurs.
Also, I'm not using any extra third-party libraries with my SQLite, so the problem isn't your Unicode extension.
Jeremy: FYI, I've just tried it with the SQLite 3.7.0 preview and the same problem occurs.
Also, I'm not using any extra third-party libraries with my SQLite, so the problem isn't your Unicode extension.
38 years ago
Jeremy: I'm having the same problem with compiling SQLite against iOS 4 for the iPad simulator, but in my case it works fine running on an actual iPad (also works in the iPhone simulator and on an iPod Touch).
Same problem with 3.6.23.1, 3.6.23, and at least back to 3.6.21. Compiling against iOS 3.2 makes it work, though that's not really an option for iPhone (as opposed to iPad) apps.
I have no idea what to do about it or how big a problem it really is...
Jeremy: I'm having the same problem with compiling SQLite against iOS 4 for the iPad simulator, but in my case it works fine running on an actual iPad (also works in the iPhone simulator and on an iPod Touch).
Same problem with 3.6.23.1, 3.6.23, and at least back to 3.6.21. Compiling against iOS 3.2 makes it work, though that's not really an option for iPhone (as opposed to iPad) apps.
I have no idea what to do about it or how big a problem it really is...
38 years ago
Pascal: The problem seems to have deep roots, however there is a solution, see the updated post. :)
Pascal: The problem seems to have deep roots, however there is a solution, see the updated post. :)
The archive
March 2011 (1)
July 2010 (1)
October 2009 (2)
August 2009 (1)
July 2009 (1)
March 2009 (1)
December 2008 (1)
October 2008 (1)
August 2008 (1)
July 2008 (3)
June 2008 (1)
May 2008 (3)
March 2008 (1)
February 2008 (3)
January 2008 (2)
November 2007 (1)
October 2007 (1)
September 2007 (1)
August 2007 (1)
July 2007 (1)
June 2007 (3)
May 2007 (1)
April 2007 (1)
February 2007 (2)
January 2007 (3)
December 2006 (1)
November 2006 (3)
October 2006 (2)
September 2006 (2)
August 2006 (1)
July 2006 (2)
June 2006 (6)
phase of matter » Blog » 2008 » January » Third » MacBook Pro keyboard response issue and Apple locking threads on their forums
MacBook Pro keyboard response issue and Apple locking threads on their forums
Thursday, January third 2008 - 12:09 • 1 update Wednesday, February 20th 2008 - 08:45
So Apple keeps shutting down consumers complaining on their forums. What a shame!
My now 14 months old MacBook Pro has an issue with the keyboard in that it awakes from sleep too slow. So if I don't type anything for a short period of time and then suddenly type something, the first one or two keys I press are not recognized. That's quite annoying, especially if you type a password, but of course not only then.
To resolve this issue I headed over to Apples discussion boards back in November 2007 - and discovered a massive thread titled ELP! - first letter always missing! discussing exactly this issue. It looked like Apple listened to their customers and released a Firmware Update December 18 to address this issue - but this didn't improve anything for me.
Today I was looking for some example cocoa code and when Google returned nothing about Cocoa at all, I realized that I only googled for "coa sample code" instead of "cocoa sample code". Obviously my keyboards behaviour has not improved at all, the first one or two letter(s) after a short typing-break are still not recognized, so I decided to post the the thread in the Apple boards again - only to see that the thread has been locked!
Obviously Apple thinks that the issue is resolved and no-one should complain any longer. Bad move, Apple! :P
Update Feb 2, 2008:
Ok, Apple today released another version of the Keyboard Firmware Update. I just installed it and it looks fine so far. Let's hope it has been fixed.
My now 14 months old MacBook Pro has an issue with the keyboard in that it awakes from sleep too slow. So if I don't type anything for a short period of time and then suddenly type something, the first one or two keys I press are not recognized. That's quite annoying, especially if you type a password, but of course not only then.
To resolve this issue I headed over to Apples discussion boards back in November 2007 - and discovered a massive thread titled ELP! - first letter always missing! discussing exactly this issue. It looked like Apple listened to their customers and released a Firmware Update December 18 to address this issue - but this didn't improve anything for me.
Today I was looking for some example cocoa code and when Google returned nothing about Cocoa at all, I realized that I only googled for "coa sample code" instead of "cocoa sample code". Obviously my keyboards behaviour has not improved at all, the first one or two letter(s) after a short typing-break are still not recognized, so I decided to post the the thread in the Apple boards again - only to see that the thread has been locked!
Obviously Apple thinks that the issue is resolved and no-one should complain any longer. Bad move, Apple! :P
Update Feb 2, 2008:
Ok, Apple today released another version of the Keyboard Firmware Update. I just installed it and it looks fine so far. Let's hope it has been fixed.
Comments are disabled
Rafael: Thank you very much, I was having a huge headache to solve the very same problem!