UIStatusBar Area Not Touchable

[torynfarr]

I've seen a few people having this problem, but so far no one has been able to resolve it.

When you hide the UIStatusBar (either in the application delegate with this line of code: [application setStatusBarHidden:YES animated:NO]; or by making a boolean entry in the info.plist file) the area where the status bar would normally be displayed does not respond to touches.



In the screenshot above, the UILabel displaying the X and Y coordinates of the touch are updated on touch and when touchmoves begin. If I slide my finder to the left edge of the screen, it's a dead zone. X stops being updated at -59 or -60... which would leave about a 20 pixel wide dead zone.

-Toryn

[scottyelich]

not to be a pain, but are you making your view be the application window size or the mainscreen size?

Scott

[torynfarr]

Here is the code that creates the UIView from within my UIViewController. I've tried two different ways, neither seems to make a difference.

- (void)loadView {
	
	UIView *containerView = [[UIView alloc] initWithFrame:[[UIScreen mainScreen] bounds]];
	containerView.backgroundColor = [UIColor redColor];
	containerView.clearsContextBeforeDrawing = YES;
	self.view = containerView;
	[containerView release];
	
}

- (void)loadView {
	
	UIView *containerView = [[UIView alloc] initWithFrame:[[UIScreen mainScreen] applicationFrame]];
	containerView.backgroundColor = [UIColor redColor];
	containerView.clearsContextBeforeDrawing = YES;
	self.view = containerView;
	[containerView release];
	
}

I think the issue has to be due to how I'm creating this view... but I'm baffled. Is the frame that initialize the UIView the incorrect one to use? From your question, it sounds like I'm initializing the UIView using the screen's frame instead of the windows.

-Toryn

[torynfarr]

If it helps, here is the code from my AppDelegate that initializes the UIViewController.

// Set up the window and main view.	
window = [[UIWindow alloc] initWithFrame:[[UIScreen mainScreen] bounds]];
mainViewController = [[MainViewController alloc] init];
[window addSubview:mainViewController.view];
	
 // Show the window.
[window makeKeyAndVisible];

-Toryn

[i.d3v1l]

as far as i have programmed it...

in the touchesBegain method... do chk that where is the touch... if it is in the desire area le it work properly and if is in the area u want to restrict... return from there...


take care and all the best... do let me know if i have done some blunder

C ya

[torynfarr]

Originally Posted by i.d3v1l

as far as i have programmed it...

in the touchesBegain method... do chk that where is the touch... if it is in the desire area le it work properly and if is in the area u want to restrict... return from there...


take care and all the best... do let me know if i have done some blunder

C ya

Actually, I'm not trying to restrict an area from being touched. Just the opposite. I want the area shown in blue in my screen shot to respond to a touch. The problem is - it doesn't. If I touch anywhere in that blue area, the event method touchesBegan does not get called.

-Toryn

[AwayBBL]

I noticed a similar effect when I used a webview with no status bar. If I show the status bar, the user can use it to scroll back to the top of the webview, but if I hide it, the area appears as dead to any touches. Maybe thats by design?

[scottyelich]

I get this same behaviour.. and I've verified that my frame is 320x480 @ 0,0.

Scott

[cpatch]

This is a known issue that's been around for a while. It even shows up in Apple's sample code...try dragging a square to the top of the screen in the Touches app. You'll notice that it drops when your finger gets to the bottom of the (hidden) status bar area. (It's more obvious in the simulator.)

[toom]

does anybody know if this problem only exists in the simulator?

[bhearn]

Originally Posted by toom

does anybody know if this problem only exists in the simulator?

Yes! The bug only exists in the simulator, oddly enough.

I put a button in the affected area, so that no part of it is touchable in the simulator, but it responds on the iPhone.

[QuantumDoja]

This is not the case for me, with 2.2 this area is still inactive.