I have run into a baffling behavior using VoiceOver. Basically when using the "swipe forward" gesture on a screen, the cursor will run off the bottom of the screen and the view will not "move" with it as it should. Worse of all, I have a button down there that is not activated by a double tap when this behavior exists.
What I can gather is that this only seems to happen on two screens, both of which feature customized appearances of the cells in a table view.
I have tried manipulating the accessibilityFrame property of these cells and these table views. I have gotten nowhere. I have tried setting the accessibilityFrame property of the cells as they are made but there was no change in behavior.
Has anyone encountered this behavior? Any ideas for trying to tackle this problem?
I've seen it, but it's not a problem, at least not in my app -- you can double-tap anywhere, not just on the button. (In other words, a blind user won't realize this is going on, because it just works.)
Related
I have a single ViewController which contains a Table View on the left and a few labels on the right. Navigating through the table view entries works fine (up/down). Focus is no problem there. Even the related text in the labels is updated just fine using tableView:didUpdateFocusInContext.
The interface looks like this:
However, the button on the right ("Jetzt ansehen") never gets focus. When I use the debugger (as suggested in the official documentation), it doesn't include the button in the focusable area at all:
I really tried to solve this using UIFocusGuide, but I have no real idea how to accomplish that, yet.
i'm trying to use the view hierarchy feature on xcode 6 to see the draggable layout of my app, but all i get is a blank area where it should be.
after trying out lots of suggestions from SO and other places, nothing works.
I have had the sim running with or without break points, different sim devices, different apps, but nothing works.
I know you're just supposed to click on the button while the app is being simulated and it's supposed to pop up, but when i do it the main interface with the button and options load along with all the elements in the debug navigator. just not the 3d UI itself.
thanks for any tips.
You can click in that view and drag by holding down the left mouse button. This gives you the 3D view.
It's not a fix, but when I had this issue I restarted Xcode and tried again a few more times it eventually worked for me.
There seems to be a recent issue as well which I've run into. When I press the button, I get an assertion failure:
Assertion failure in -[UITextView _firstBaselineOffsetFromTop]
There's an OpenRadar here with a workaround which worked for me of attaching a "useless" constraint" in ViewController.m:
if ([NSLayoutConstraint respondsToSelector:#selector(activateConstraints:)]) {
TEXTVIEWNAME.translatesAutoresizingMaskIntoConstraints = NO;
[NSLayoutConstraint activateConstraints:[NSLayoutConstraint constraintsWithVisualFormat:#"H:|-[TEXTVIEWNAME]-|" options:0 metrics:nil views:NSDictionaryOfVariableBindings(TEXTVIEWNAME)]];
}
After clicking "Debug View Hierarchy" button, you are on the blank white screen.
Click on thread option depicted in below image, list will open, select any option from list, and again click on "Debug View Hierarchy" button.
Screen will render.
This is what works for me.
I know this is really old now, but this is still occurring for me. At first, I only saw a spinner when clicking on the debug view hierarchy. But, when I tried the steps above to click on my equivalent to the "0 mach_msg_trap" above, and then back on the debug view hierachy, the spinner went away. This was an improvement since I was not just staring at a spinner now that seemed to never stop spinning no matter how long I waited ( 20 minutes for example ). However, at this step now, the screen is blank, just like stanley mentioned above. So, I still cannot see any useful debug information.
One thing I will note is that what I am trying to view is inside a webview. Webviews cause our xcuitests lots of problems, that we eventually do solve. But, they do not play as nicely as other objects. I mention the webview because of this just in case it's the actual reason I am not seeing anything displayed in the debug view hierachy.
I'm part of a team building a mobile web app using AppGyver Steroids (PhoneGap). We are having an issue with the iOS7 keyboard displaying a very faint "Done" button on the keyboard when the user is operating in a text area or an input select. I suspect this is a problem that is actually global in our app, but these are the instances where I have observed them.
I've searched and searched for a solution or how to "customize" the keyboard in order to make this "Done" button more obvious, but I haven't found any solutions yet. Can anyone point me in the direction of how to adjust the "Done" button or any other keyboard/input controls?
Attached are two screenshots showing the issue.
http://i.stack.imgur.com/KeFYM.png
http://i.stack.imgur.com/h11IH.png
Have you seen the issue on github? It's now fixed. They'll be including the option for custom colours in the near future.
I been trying to debug a problem with some odd behaviour inside a UIWebView. My app uses a UIWebView to display a custom form to collect certain information. When the form is first loaded, filled and submitted, everything behaves as it should. After the first submit, when the form is reloaded, the keypad will not display (but the content scrolls as though it is).
The only solution I have come across is here, but this does not seem like the solution to my problem since that line is already in my app delegate.
Is this a known issue? I don't even know where to start looking to debug this issues.
After much searching SO and Apple forums, it was the view hierarchy that was getting rearranged. In my particular case, a progress indicator was being added as new window (by a coworker, so I can blame someone else for this). The trick was not set this new as the key window and only manipulate the the hidden properties
This is just a quick fix because it was only one line of code that was causing this major problem.
I have an application that allows the user to edit multiple text fields and views. Rather than mess around raising each view to the top when the keyboard is active, I decided to instead make one textView for editing and hide/show it when input is needed, then transfer the data when it is done. To move focus to the new textView, I call its becomeFirstResponder method, and lo and behold, the cursor goes to the right place. However if I use this method, the iPhone keyboard does not appear. I have no idea why. Can anyone explain, and tell me how to make the keyboard appear? All the other questions I've looked at seem to indicate that setting becomeFirstResponder for a textView ought to make the keyboard come up.
-Ash
Is Hardware -> Simulate Hardware Keyboard enabled?
Are you doing this whole thing programatically or using Interface Builder as well?
If so are the IB connections setup right?