I've posted separately about the glitchiness of the live.dial and the live.slider which appears as a single multislider style slider.
I'd like to point out that the kslider will not render the top or left edges on the ipad 1 - this is irrespective of the actual or relative sizes of the mira.frame object or kslider object. Indeed the Frame of the kslider is so thin it needs to be 'on' to discretize between adjacent 'white' keys. This is in part a Max6 issue because with 4/5 (from memory) you could easily use kslider without a frame. Either way, those two edges are not rendered on my ipad 1
The slider also renders differently than in max (again like a bar multislider style) - not sure why this has to be so - some interfaces work better with the line
On the ipad 1 usability front, for those interested, apart from a few incompatibility issues (regarding lack of compass etc) the updating speed (even with the help file examples) can be very slow (there may be network issues, but they don't blight other apps!) - it can take quite a few seconds to populate the screen
Most objects appear live (as if by magic) but i've found the fpic object to be hit and (mostly)miss
Hopefully we can have a 'mira compatible' object filter in the Max object explorer soon (the little (m) is handy, but you still need to hunt a bit too hard)
FWIW, I hope the dev(s) work mostly on fixing what we already have (efficiencies) before getting distracted by additional bling ..... it crashes too often !!!!!!!!!!!!!!!!!