What is the difference between "User Interaction Enabled" in the Identity Inspector as opposed to the "User Interaction Enabled" in the attributes inspector? They are not linked and only the latter seems to have any effect.
Check out the explanation given here:
Xcode: Why does "User Interaction Enabled" appear twice?
Related
After pressing ctrl+shift+c in both cases the Inspector tab opens if it's closed. The difference is that in regular Firefox the "Pick an element from the page" is activated while in aurora Firefox it isn't.
I thought that the given shortcut is for the "Pick an element from the page" and ctrl+shift+I is for Inspector tab. So first thoughts was that something is broken, tried searching for it - nothing (maybe wrong keywords or smth). Compared my settings on both of them - nothing. Then I came across few bugzilla reports one of which even asked for that feature. So now I'm lost.
Is ctrl+shift+C supposed to be a shortcut to "Pick an element from the page" or not? Based on this no, but then why does it work like that on regular Firefox?
Which of the two behaviors is the right one?
Thank you for your time.
This is a known issue being tracked in this bug.
I have two buttons (one is standard button caption"OK" and another is custom control button caption "Submit") in my win32 application. JAWS screen-reader is speaking out correctly the standard button "OK Button, To activate press space bar" but for custom button it is speaking only "Submit" not speaking "Submit button, to activate press space bar".
Can you tell me a way by providing any samples or documents to support this accessibility issue in win32 application. I am new here.
Thanks in advance.
If I give my Applescript to another person, they would have to manually allow Applescript control of their computer by going into System Preferences, clicking Security & Privacy, then clicking Privacy and then Accessibility, then finally add Applescript. Is there anyway I can make Applescript add its self so they don't have to? Is there another solution? Because without them doing this, Applescript can't click things.
Without applescript added so it can have control, I get the error, "Script Editor is not allowed assistive access."
I believe that your are trying to enable assistive access for devices. For instance, GUI scripting requires this to be enabled. You can't enable it directly, but you can point the user to the place they need to go. The following finds out if assistive access is enabled and brings up the System Preference pane where the option is.
tell application "System Events"
set UI_enabled to UI elements enabled
end tell
if UI_enabled is false then
tell application "System Preferences"
activate
set current pane to pane id "com.apple.preference.universalaccess"
display dialog "This script utilizes the built-in Graphic User Interface Scripting architecture of Mac OS x which is currently disabled." & return & return & "You can activate GUI Scripting by selecting the checkbox \"Enable access for assistive devices\" in the Universal Access preference pane." with icon 1 buttons {"Cancel"} default button 1
end tell
end if
That should be enough for your users to get the hint.
You can theoretically do it via the command line:
https://raymii.org/s/snippets/OS-X-Enable-Access-for-assistive-devices-via-command-line.html
For example, in Lion and Mountain Lion it's a simple as this:
touch /private/var/db/.AccessibilityAPIEnabled
Full Keyboard Access mode is enabled or disabled in the Keyboard preference pane - it's referenced here:
Efficiently subclassing standard Cocoa controls
and here:
Disable Full Keyboard Access for App
but nowhere on the web have I found out how to determine, within my app, if Full Keyboard Access is enabled. I'm writing a custom radio control and want to allow tabbing into it iff Full Keyboard Access is on.
In Mac OS X 10.6 or higher: -[NSApp isFullKeyboardAccessEnabled].
As best I know this is undocumented. It is stored in AppleKeyboardUIMode in NSGlobalDomain:
defaults read -g AppleKeyboardUIMode
It's a bitfield, but I've never seen docs for it. "Full Keyboard Access" seems to toggle bit 1 (value=2).
The short is you should be able to fetch this from NSUserDefaults and bitmask it to find your answer, but it could change.
I have a document with connection information to a device over a serial port. It specifies "full duplex" as the setting for flow control. Under Windows, I have the following options for setting up the flow control:
Xon/Xoff
Hardware
None
What is the equivalent of "full duplex" in the above list?
"xon/xoff" is a synonym of "software flow control" (as opposed to "hardware flow control").
"full duplex" means "in both directions"; theoretically you can enable software flow control or hardware flow control in one direction only (i.e. "half duplex"), or in both directions ("full duplex") ... so there's not enough information to answer the question.
What kind of device is it? If I had to guess, my first guess would be "hardware" flow control, simply because "software flow control" is less compatible than "hardware flow control" with transferring binary data.