Hi Quincy, Alex and list, Quincy, thanks very, very much for your explorations here.
Like Alex, I am also a blind developer and have felt for a long time, that if more sighted people were aware of the insane amount of cognitive load that a blind or visually impaired software developer needs to go through with XCode (and other IDEs) on a regular basis just to get the simplest things done, then it would be a huge step to making this situation better for all blind devs. For myself, I just wonder who at Apple thinks this sort of excruciating process is at all a palatable idea or worse yet, a desirable one! Apple has the choice of the cream of the crop in terms of UX designers so as you say, I think somebody really needs a dope slap! ;) I am fortunate that other members of my development team are sighted so a lot of the UI craziness is not something I need to worry about in order to finish projects but there are many of us working on our own who do not have that luxury. -And honestly, in the end, no one blind, should be essentially forced to rely on someone sighted to do something that should really be simple for everybody. As you have seen, the crazy complexity of clicking and dragging, for a visually impaired person is essentially in direct inverse proportion to the relative ease a sighted person experiences. anyway, enough from me. :) thanks very much for sharing your tips for Voiceover use and also, thanks for sharing your experience so that others are enlightened by it! You rock! :) Have an awesome weekend! Cheers! Cara --- iOS design and development - LookTel.com --- View my Online Portfolio at: http://www.onemodelplace.com/models/Cara-Quinn Follow me on Twitter! https://twitter.com/ModelCara On Nov 26, 2015, at 8:47 PM, Quincey Morris <quinceymor...@rivergatesoftware.com> wrote: On Nov 26, 2015, at 18:11 , Alex Hall <mehg...@icloud.com> wrote: > > Moving Controls in the Outline Table Well, that was a scary experience. There’s a lot more going on there than meets the eye (excuse the expression, but it’s literally true in this case). 1. That “invisible button” on the right isn’t an invisible button, it’s another column in the outline view. It’s empty in most rows, but in a top-level row (like Window), it actually contains a button that causes the auto-layout errors to be displayed. (The outline view slides over to the left, and the auto-layout errors list slides in from the right.) If there are no auto-layout errors, the button that’s there is invisible, though it still works. (!) The virtue of going to this column, in your instructions, is that it isn’t an editable outline view cell, so you can’t accidentally start editing text, as happens if you try using the main column. (The column to the left of the main column is the disclosure button, of course.) 2. What happens when you press the Control key during dragging in an outline table is that the selected row, which got is selection dimmed when dragging starts, gets its selection undimmed and you can’t drop. I dunno why. 3. What happens when you press the Command key during dragging is — exactly nothing. 4. What happens you press Command *and* Control during dragging — depends on which outline view it is. In the navigator pane, it works like plain Command (does nothing). In the object outline, it works like plain Control (disables dropping). Cases 2 through 4 are the behavior using an actual mouse/trackpad. Continuing on with VO: 5. What happens when you unlock the mouse to end the drag, given that you have Command+Control held down because VO, is the same as #4 (i.e. nothing) *except* when you drag between scenes, in which case it works. (!) VO summary: — You can rearrange a regular outline view like the navigator pane. — You can’t drag into the IB object outline, except… — … in the unique case of VO dragging between scenes, you can. Executive summary: — You can’t drag an object out of the object library using VO, at least not by dragging it. I kept the best till last: 6. Although VoiceOver Utility is configured to allow Command+Control *or* Caps Lock as the VO modifier, Caps Lock doesn’t actually do that on my Apple keyboard. If the light is on, it goes out when VO is enabled, so something thinks it’s trying, but it doesn’t actually work. If it did, it would solve all of the above by avoiding the need for Command or Control to always be down. Somebody in Cupertino needs a dope slap, I think. _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/caraquinn%40caraquinn.com This email sent to caraqu...@caraquinn.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
