Wedge

Public area => Bug reports => The Pub => Archived fixes => Topic started by: live627 on November 21st, 2012, 04:59 AM

Title: Editor method add_button does not set button class
Post by: live627 on November 21st, 2012, 04:59 AM

Title says it all I think.

Title: Re: Editor method add_button does not set button class
Post by: Arantor on November 21st, 2012, 05:02 AM

Fairly sure the method long predates buttons being able to have spiffy classes. Not a hard fix but I'm reluctant to use my PC with a suspected failing fan, hoping to get it replaced tomorrow.

Guessing classes should be an optional extra? Want onclick with that (if it doesn't do it already)?

Title: Re: Editor method add_button does not set button class
Post by: live627 on November 21st, 2012, 05:13 AM

Yes, it should be optional.

Sucks about the fan. Especially if it's a CPU fan.

Title: Re: Editor method add_button does not set button class
Post by: Arantor on November 21st, 2012, 05:22 AM

Well, it's not an enormous problem, the late 2011 MacBook Pros (at least the 15" and 17" as far as I can tell) all use the same pair of fans, one for the CPU, one for the GPU. I'm covered by AppleCare, so it is a case of checking them have them in store then taking it in for them to replace it... in theory.

Title: Re: Editor method add_button does not set button class
Post by: Arantor on November 26th, 2012, 01:08 AM

Added it locally. I'm still running on a fan with partial power, waiting for another to be in store >_<