OK, thanks again.
I’ve run out of space on my drive and my boss wants me to run El Kapitan, so
I’ll try this again once I’ve got the new drive and O/S in place (hopefully by
tomorrow).
Best wishes.
Tim Burgess
From: program-l-bounce@xxxxxxxxxxxxx [mailto:program-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Yuma Decaux
Sent: 04 April 2016 19:56
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: Reading errors in XCode
Hi,
ot sure maybe I didn't get you right. You want to go to the console for
checking logs right? If you have an opened xcode project and press command run
having issues, normally it puts you into the issue navigator with a table where
the issues reside. Either you directly arrow up and down the issues or interact
and vo up down to each. if the fix it pop up appears, press escape. If you want
to go to that line of error, with the error highlighted press command-j which
will go to it.
If however you run and have had some prints successful or have an exception or
runtime error somewhere, there are two boxes next to each other in the debug
navigator which is command-6. With the vo key combo I told you
which is uninteract, vo right till you hear "editor area", interact, go all
the way right till you hear "debug", interact and vo right till you hear debug
console". If you vo left twice from there you have the variables view which is
very useful as the break points are pretty much there for you, if you make sure
to check break points at all exceptions in your break point editor. note: turn
off your break points sometimes when the error is from a lower abstraction
layer as you won't get any messages in the console such as nil returns or other
issues.
Cheers,
On 4/04/2016, at 10:46 PM, Tim Burgess <tim@xxxxxxxxxxxxx
<mailto:tim@xxxxxxxxxxxxx> > wrote:
Hi,
Things don’t seem to work like you describe on my system.
Pressing Esc when focused on an issue doesn’t offer me any fix options, I’m
afraid.
When trying to navigate to the console, I hear “No editor” when I’d expect to
find the Editor area.
Any ideas?
Best wishes.
Tim Burgess
From: <mailto:program-l-bounce@xxxxxxxxxxxxx> program-l-bounce@xxxxxxxxxxxxx [
<mailto:program-l-bounce@xxxxxxxxxxxxx> mailto:program-l-bounce@xxxxxxxxxxxxx] ;
On Behalf Of Yuma Decaux
Sent: 04 April 2016 09:57
To: <mailto:program-l@xxxxxxxxxxxxx> program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: Reading errors in XCode
You will need to see them. Just press escape as each issue will pop up a fix
suggestion.
console is in the debug viewer. The combination is command-6 uninteract, vo
right till you hear "editor area", interact and right to end till you hear
debug, interact and right once . You will be in the console.
There's also a quick map key which I don't use that normally takes you straight
to the console but I'm not sure of the key combo.
There's probably another way which is to set a window spot where the console is
so you can nav to it with a shortcut of your choice through the voice over
utility.
Cheers,
On 4/04/2016, at 5:29 PM, Tim Burgess < <mailto:tim@xxxxxxxxxxxxx>
tim@xxxxxxxxxxxxx> wrote:
Hi
If I build my XCode 7 project and errors are encountered, they appear as a
table in the Issue Navigator. Each cell of the table can be an expandable item
which reveals the error information.
The problem that I’m hitting is that the error text goes beyond the right edge
of the window and I can’t figure out how to get VoiceOver to scroll to see more.
I’m told that a better approach would be to use the Log Navigator, but I can’t
find a keystroke to take me there on-demand and using VoiceOver navigation is
just too slow to satisfy the productivity requirements of my employer.
Can anybody offer any help, please?
Best wishes.
Tim Burgess
