How do I turn off the instant search in Xcode 4's Documentation? Everytime I pause my typing, I have to wait for too long (sometimes 30 seconds, honestly) before I can type some more. If that's how long it takes, I'd rather just hit enter to search.
Thanks in advance!
If you didn't have so many documentation sets downloaded or, more importantly, selected to search when you are typing into that Search field... you wouldn't experience the download.
Click on the magnifying glass icon there and you can change "Find Options" to only look at the documentation sets that are most relevant to you (whether Macintosh or iPhone, and whether 10.6 or 10.7, iOS 4 or iOS 5).
(I cribbed my answer from this question). Hope this helps you out!
Related
So basically i use emmet and coc-completions as a neovim developer in termux (it's an android app that runs linux environment). Today all of the sudden, my ctrl-y button started taking 2-3 sec to even execute. Lemme elaborate what i mean .
enter image description here
Whenever i click ctrl-y, a big "Y" letter comes on the screen and stays for 2 seconds. Which earlier didn't show up and it literally used to take half a second or less. I recall so many things i did before this happened, i am not sure what made it happened. If you have any idea please any help would be greatly appreciated.
So basically what i did is i changed the mapping of emmet code writer to tab from "". The problem now arises with tab, but i don't care as "" is working. Thanks to the guy who helped me :)
I wanted to go through QtQuick/QML Button API, which I found here online.
But I can't find it from the offline documentation available in QTCreator. The offline search gives me less relevant results.
Any tips for searching...? Thanks!
One trick I use is this:
Type the item (e.g. "Button") into the code editor
Hover my mouse cursor over the item
Press F1
That will open the documentation for the Button QML type. Works in C++ too.
Google has much more powerful search engine comparing to offline documentation browser. So you just didn't find matching article in help browser search. You can:
Find "Button" instead of "button" in help browser search results
Place cursor on interesting identifier in code and press F1 to show help
Select appropriate documentation in "Contents" mode of help browser left panel
I'm working on a web application and I want to make it easy to use via screen reader.
Testing stuff in JAWS is time consuming.
Is it possible to make JAWS display text instead of reading it?
I don't want actually to hear the content during development.
I just want to see what would be read by JAWS.
There is no speech viewer for Jaws, as far as I know. However, you can make it write all speech output to a log file using the "/z" switch. Unfortunately, you cannot view the log file in a text editor while the screen reader is running, because it is locked.
Open a command prompt or bring up the Run dialog by pressing Win+r and type:
"jaws_executable" /z"log_file"
Where "jaws_executable" is the full path and file name of the Jaws application and "log_file" is the location and name of the speech log file.
Important: There should be no space between "/z" and the log file name.
This is an old thread, but since it came up top in my search I thought I'd update it. JAWS 15 has just introduced this capability through the "Speech History" feature. Follow these directions to enable it:
If you miss one or more messages spoken by JAWS, you can press
INSERT+SPACEBAR, followed by H to open a Results Viewer window
containing up to the last 50 announcements spoken by the synthesizer.
When the Speech History window opens, you are placed on the line
containing the most recent announcement. To clear the history, press
INSERT+SPACEBAR, followed by SHIFT+H. The history is also cleared when
you lock the computer or completely log off. If you do not want JAWS
to maintain a speech history, clear the Enable Speech History check
box in Settings Center.
Read more in the JAWS 15 What's New document under New Speech History for Speech-only Users.
For those of you stuck with JAWS 14, Nektarios Paisios answer using the "/z" log worked best for me.
I believe there is a visual indicator in JAWS, but my version of JAWS is being a bit wonky. These days, NVDA plays pretty similarly to JAWS, so you can use that, and it has a speech output console: Right click the NVDA icon in the system tray, select Tools, and Speech Viewer.
The easiest way to see what a screen reader 'sees' is to disable the CSS. This will show you everything on the page that the screen reader can access. This will give you a good idea what is going on during development until you want to get into the more complicated stuff.
See http://www.iheni.com/quick-tip-testing-web-content-for-screen-readers-without-a-screen-reader/. This site has a lot of useful info too http://webaim.org/articles/.
You can enable the Braille Viewer in Start Menu > All Programs > JAWS 14.0 > Braille Viewer.
Braille Viewer will render visual text output of what would be sent to a braille display. It sometimes uses abbreviations or shorthand but is a close representation of the speech output.
Also take a look at Fangs Screen Reader Emulator for Firefox. It will render a text output of what a screen reader would announce on a page, in the correct read order, though it does not render dynamic content.
JAWS is supplied with a Braille Viewer in the 'Utilities' folder, which will render any text from the focus.
this link
indicates that it is ctrl+cmd+up or down just like xcode says but mine seems to be revealing in finder even though the shortcut says otherwise.
Anyone else having this issue? How do you fix it.
Instead of using key combinations I like to use gestures for most of these kinds of actions in Xcode. For this one simply slide 3 fingers up or down and wait a moment. It will switch between the header and implementation file. I find it works very well on a Macbook Pro trackpad or my Magic Trackpad which has the enough space for these gestures. If you have a Magic Mouse you may not have enough space for this and other gestures.
I think you will find it easier to remember this gesture over the key combinations.
My problem is that when ever the iPhone has to push a view (like the keyboard) it takes a really long time (15+ seconds).
I never used to have this problem with the simulator, but after I updated xcode to 3.2.3, the simulator is almost un-usable for anything which requires a keyboard.
For example, on the simulator the springboard app (the one which stores your icons and has the search pane to the far left). When I scroll all the way over to the search, the keyboard pops up immediately but it takes a very long time for it to register any taps and the entire simulator becomes unresponsive.
This happens with any app.
Also, sometimes it can take a very long time for the keyboard to even show.
I'd really appreciate any thoughts!
In my case this was being caused by the NSZombieEnabled flag. Try disabling that if you have it set and the MKMapView may come "back to life".
EDIT: Unfortunately my problem just came back, so the above did not solve this problem. Sorry!
Finally solved this over here. In my case it was caused by a bad stick of RAM. OWC has a good article about checking for bad RAM DIMMs over here: http://eshop.macsales.com/Search/displayFAQDetails.cfm?ID=355 - maybe worth a shot. I re-seated my 2 risers in my Mac Pro, and the simulator is buttery smooth again!
Remember that using shiftkey you can toggle simulator animations slower or faster
pushing down shift for about 2 to 3 seconds toggle simulator to slow/fast animation