(And no, the simulator doesn't have this support -- so testing this would require plumbing in a synthetic data stream or some sort of unit test data source. Still a pretty primitive ecosystem.)
Anyway, this is what the screen looks like for the ttl application (actual screen dump from the watch itself):
Other notes:
- Debugging is exceptionally difficult. The screen dump from above was from one of only two sessions that have actually worked on the real hardware. The profile reset was only part of the problem. Disabling "diagnostics to apple", iMessage, HeySiri, etc. all seem to help kick in one more session. Perhaps the reliability of debugging is a function of the network between the watch and the phone. Or still we're stuck in beta ware.
- The iPhone5 may be part of the problem -- not the speediest machine out there.
- You will notice that the above right columns are in SF font and are not constant width. I do have an outstanding project to understand the best way to get constant width working for numbers as mentioned during the SF font overview.
No comments:
Post a Comment