For the basic case, I think an Accessibility Container isn't needed, because the objects are laid out in a top-to-bottom and left-to-right way. But we can't always depend on that.

Yesterday I mowed the front lawn, today the back, which was upwards of 20" tall in places, due to a couple of light rains we've had.

  --

Yesterday I did some bug hunting in the morning, and reading through the literature on the Xcode debugger, "Instruments". Although I am getting a small increase in memory usage, per hand play, it doesn't show up as a 'leak' per se. As far as I can tell it may just be the OS not releasing some cached image data - this is apparently a known issue with iOS. Hmmm.

After that I fiddled with Voice Over and Auto-Scan tools.

Work-wise, today, it's getting external switches working for the app. This is all under Apple's "Accessibility" initiative, and it's not particularly attractive under the hood. But it's the game and I'll have to play it.

Right now I'm just playing around with the Accessibility Container stuff. There will probably be several different interaction modes, but the container is necessary for most of them.

It's been a while, but why not?

Keeping busy.

Computer lab and school yesterday.

Today it was changing the water in the turtle tank (5 gallons, once a week), mowing the front yard (it's getting warm out!), and doing end-of-the-month bills (depressing).

-----------

Updated Yosemite last week, but lost the Win7 partition. When I went to re-install Bootcamp the (mid-2012) MacBook Pro froze in the partitioning process. Yikes. I was able to reboot into Yosemite, but I can't afford to have a dead development machine, so no Win7 for now.

Which is a problem, because Adobe After Effects needs a 64 bit box. I could, if I was crazy, run Creative Cloud on the MacBook, but I'm not crazy so I won't.

No Adobe products on mission critical or internet enabled machines....