You might consider displaying things "normally" on the screen, but adjusting an
accessibility property like Description. In there, replace the odd strings with
text that VO will read normally. Visually, it'll look normal, and audibly/in
braille, it'll read normally. That's all I can think of.
>
Bingo. Ternary operators.
Thanks all.
On Jan 6, 2016, at 5:45 PM, Alex Zavatone wrote:
> Hi all. I was just extending some of my configuration file support on iOS to
> add move from one config file to one master and then a product specific one.
>
> So, in the master, i'll have the full set
Hi all. I was just extending some of my configuration file support on iOS to
add move from one config file to one master and then a product specific one.
So, in the master, i'll have the full set of changeable properties defined in a
pList and after reading this into a dictionary, I'll assign t
On 14 Oct 2015, at 2:27 PM, Shane Stanley wrote:
> On 14 Oct 2015, at 1:33 PM, Graham Cox wrote:
>>
>> I’ve been passing nil forever, only now does Xcode 7 complain, presumably
>> because only now is the _Nonnull attribute added. But either the
>> documentation or the addition of _Nonnull is
At runtime all bets are off anyway.
Nullability is a compile time constraint for Objective-C and a helper for Swift
overlays.
You can still pass an object in runtime in Objective-C.
It's up to the receiver to handle it.
Sent from my iPhone
> On Jan 7, 2016, at 1:32 PM, Shane Stanley wrote
