Comments on: Is UIButton’s backgroundImage broken? http://www.24100.net/2009/02/is-uibuttons-backgroundimage-broken/ Ralf Rottmann – CTO at GrandCentrix, Blogger for The Next Web, iOS and Android Developer, Social Media Addict Sat, 10 Dec 2011 16:21:29 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: chris http://www.24100.net/2009/02/is-uibuttons-backgroundimage-broken/comment-page-1/#comment-191 chris Mon, 06 Apr 2009 15:10:22 +0000 http://www.24100.net/?p=288#comment-191 hey.. Im having a nightmare with Images in buttons myself, UI Classes should be the easy stuff to deal with in a project! I wonder if you would explain how you are using a TTF in your app? I didn't think this was possible... hey.. Im having a nightmare with Images in buttons myself, UI Classes should be the easy stuff to deal with in a project!

I wonder if you would explain how you are using a TTF in your app? I didn’t think this was possible…

]]> By: Jean-Sebastien http://www.24100.net/2009/02/is-uibuttons-backgroundimage-broken/comment-page-1/#comment-185 Jean-Sebastien Thu, 02 Apr 2009 17:41:32 +0000 http://www.24100.net/?p=288#comment-185 Oh, I forgot the (dirty dirty hack like) solution Just add "[self bringSubviewToFront:myView];" in a subclass of the button's "layoutSubviews". This require a hard reference to myView, but thats easier than laying out subviews by hand from the controller. Oh, I forgot the (dirty dirty hack like) solution

Just add “[self bringSubviewToFront:myView];” in a subclass of the button’s “layoutSubviews”. This require a hard reference to myView, but thats easier than laying out subviews by hand from the controller.

]]> By: Jean-Sebastien http://www.24100.net/2009/02/is-uibuttons-backgroundimage-broken/comment-page-1/#comment-184 Jean-Sebastien Thu, 02 Apr 2009 17:24:10 +0000 http://www.24100.net/?p=288#comment-184 @ Corey : This is broken. A "background" view should be in the background. If this is expected behavior, Apple is more moronic than I expected. Overlaying views ABOVE the button is all fine and dandy, until you realize that you need to manually calculate their positions when layourSubviews gets called after a screen rotation. Add to that the fact that you need to fake the button's state, and you are reinventing the wheel. Saying that this is expected behavior doesn't make any sense. @ Corey : This is broken. A “background” view should be in the background. If this is expected behavior, Apple is more moronic than I expected.

Overlaying views ABOVE the button is all fine and dandy, until you realize that you need to manually calculate their positions when layourSubviews gets called after a screen rotation. Add to that the fact that you need to fake the button’s state, and you are reinventing the wheel.

Saying that this is expected behavior doesn’t make any sense.

]]> By: Corey http://www.24100.net/2009/02/is-uibuttons-backgroundimage-broken/comment-page-1/#comment-10 Corey Tue, 17 Feb 2009 20:42:16 +0000 http://www.24100.net/?p=288#comment-10 I ran in to this problem... I went to the Tech Talk in Toronto, and asked an engineer about my button problems (forgot his name). He basically told me that was expected behavior, and I should go about it another way. He kind of just glazed over it, but that made me rethink my interface. My suggestions are (none of which you will be happy about): 1. If you only have a few buttons on the screen, don't make your custom labels a subview of the button, make them a subview of the buttons superview. 2. If you have a lot of buttons (I have over a hundred, a periodic table in case that seems crazy) and are worried about killing the processor with doubling the amount of views on screen, don't use UIButton, use UIView or UIImageView. You can "fake" button like behavior by overriding the toucheBegan, touchesEnded, touchesMoved methods. A little bit of a chore but gives you the flexibility you want. Good luck. I ran in to this problem…
I went to the Tech Talk in Toronto, and asked an engineer about my button problems (forgot his name). He basically told me that was expected behavior, and I should go about it another way. He kind of just glazed over it, but that made me rethink my interface.

My suggestions are (none of which you will be happy about):
1. If you only have a few buttons on the screen, don’t make your custom labels a subview of the button, make them a subview of the buttons superview.

2. If you have a lot of buttons (I have over a hundred, a periodic table in case that seems crazy) and are worried about killing the processor with doubling the amount of views on screen, don’t use UIButton, use UIView or UIImageView. You can “fake” button like behavior by overriding the toucheBegan, touchesEnded, touchesMoved methods. A little bit of a chore but gives you the flexibility you want.

Good luck.

]]> By: Sal http://www.24100.net/2009/02/is-uibuttons-backgroundimage-broken/comment-page-1/#comment-9 Sal Tue, 17 Feb 2009 17:13:37 +0000 http://www.24100.net/?p=288#comment-9 I found the same thing when setting the background for a tablecontrollers navbar. Essentially, whenever I added a subview to the navigationBar, the 'Back' button wouldn't respond to touches. I wound up adding a UIImageView to the navigationBar instead of just a UIView. That solved the problem of the image being the top layer. I found the same thing when setting the background for a tablecontrollers navbar.

Essentially, whenever I added a subview to the navigationBar, the ‘Back’ button wouldn’t respond to touches.

I wound up adding a UIImageView to the navigationBar instead of just a UIView. That solved the problem of the image being the top layer.

]]> By: CJ Millisock http://www.24100.net/2009/02/is-uibuttons-backgroundimage-broken/comment-page-1/#comment-8 CJ Millisock Mon, 16 Feb 2009 22:20:07 +0000 http://www.24100.net/?p=288#comment-8 Yes, that is broken. I'd say file a bug report. Yes, that is broken. I’d say file a bug report.

]]>