I have an early 2011 and have had this problem twice. The latest time I was working in SF and didn't think they would replace the logic board again for free, it being three years out of warranty. They did, which suggests to me that internally Apple has been aware of this problem for quite some time. This program gives me relief because I can see the problem happening again.
If I remember correctly the store said it was due to loose connections between the logic board and the discrete graphics. It originally manifested as lockups as soon as the discrete GPU kicked in. For anyone else seeing this problem, I was able to manage that using a tool called gfxCardStatus which disables the discrete GPU.
I'm pleased that Apple is doing the right thing by their customers and offering to reimburse historical repairs.
I had a 2007 MacBook Pro, it had the original round of Nvidia issues. I got one from a friend in 2013. Originally I was going to use it as a parts machine because I wanted the CD drive, but instead I realised it may have the Nvidia issues. I brought it into Apple and it popped for the issue, so they sent it off, I got it back and it was fully functional again. No charge.
Are developers allowed to use these resources freely in their own apps? I ask because "look and feel conflicts with first-party apps" has been grounds for rejection in the past.
mmm... Good point, nevertheless you can already use some resources (like the refresh button, or the favourites icon). But icon, popover background, textures, buttons, should be safe because they're not too branded.
For settings icon, it should be more prone to be rejected...
I don't think there really is a clearly defined boundary here.
I've worked on projects at past jobs where the designs demanded that we duplicate the look and feel of certain iOS system APIs and programs to a T. Apple passed those through approval without making a sound about those bits.
On the other hand, Tapbots has had an app rejected in the past for using a clock icon that looked a little like Apple's[1], back in 2009. And that wasn't an exact copy.
We're not going to get an official statement from Apple on this, so the best I can suggest is to tread with caution. Better to be inspired by than to flat out copy.
Ruby also lets you do this in function definitions. Python doesn't special-case the underscore like Ruby does -- while I have occasionally wished otherwise, it is at least consistent with Python's language design principles that the special case doesn't exist.
I don't have a source for this, but it is my understanding that, even though the python interpreter doesn't special-case the "_" variable name, it is a convention to use the underscore in the same situations in python as are described in ruby in the article.
Apart from the special meaning of the underscore in interactive mode, and the function _() in Django, I don't think it's common to use _ as a placeholder in Python. I sometimes do it regardless, hoping its meaning should be clear enough, but it's less suitable than in Ruby because you can't use it to ignore multiple arguments.
If I remember correctly the store said it was due to loose connections between the logic board and the discrete graphics. It originally manifested as lockups as soon as the discrete GPU kicked in. For anyone else seeing this problem, I was able to manage that using a tool called gfxCardStatus which disables the discrete GPU.
I'm pleased that Apple is doing the right thing by their customers and offering to reimburse historical repairs.