Okay, that's what I am doing right now. Only in one circumstance will my app
require the device to change orientation for it to look correct so I guess
that's not too terribly bad.
Eric
On Thu, Jan 21, 2010 at 12:47 PM, Luke Hiesterman <luket...@apple.com>wrote:
> If you use autorotation you guarantee that your own app's rotation follows
> the same patterns of the system apps and thereby what the user is used to
> and expects. While a flat phone is by nature ambiguous from an interface
> orientation perspective, following the system's lead is the best path here.
>
> Luke
>
> Sent from my iPhone.
>
> On Jan 21, 2010, at 9:36 AM, "Eric E. Dolecki" <edole...@gmail.com> wrote:
>
> Wouldn't autorotation fall into the same category of problem? Should I also
> look into device rotation in tandem with orientation just in case
> orientation fails?
>
> On Thu, Jan 21, 2010 at 12:17 PM, Luke Hiesterman < <luket...@apple.com>
> luket...@apple.com> wrote:
>
>> UIViewcontroller with autorotation is the best way to do this. Then you
>> don't need to deal with UIDevice orientations.
>>
>> Luke
>>
>> Sent from my iPhone.
>>
>>
>> On Jan 21, 2010, at 8:30 AM, "Eric E. Dolecki" < <edole...@gmail.com>
>> edole...@gmail.com> wrote:
>>
>> I am sending a view orientation data which works great, if the phone is
>>> held
>>> up...
>>>
>>> UIDeviceOrientation orientation = [[UIDevice currentDevice] orientation];
>>>
>>> if( orientation == UIDeviceOrientationLandscapeLeft || orientation ==
>>> UIDeviceOrientationLandscapeRight ){
>>>
>>> [myView iAmLandscape:YES];
>>>
>>> } else if(orientation == UIDeviceOrientationPortrait) {
>>>
>>> [myView iAmLandscape:NO];
>>>
>>> }
>>>
>>>
>>> However if I have the phone angled back almost flat in my hand, it isn't
>>> caught ... UIDeviceOrientationFaceUp and UIDeviceOrientationFaceDown seem
>>> to
>>> screw this up. When some people use their phone, they hold it flat in
>>> their
>>> hand which seems to produce an orientation of face up, but doesn't
>>> provide
>>> portrait or landscape information.
>>>
>>>
>>> What's the best way to tackle this?
>>> _______________________________________________
>>>
>>> Cocoa-dev mailing list ( <Cocoa-dev@lists.apple.com>
>>> Cocoa-dev@lists.apple.com)
>>>
>>> Please do not post admin requests or moderator comments to the list.
>>> Contact the moderators at cocoa-dev-admins(at) <http://lists.apple.com>
>>> lists.apple.com
>>>
>>> Help/Unsubscribe/Update your Subscription:
>>> <http://lists.apple.com/mailman/options/cocoa-dev/luketheh%40apple.com>
>>> http://lists.apple.com/mailman/options/cocoa-dev/luketheh%40apple.com
>>>
>>> This email sent to <luket...@apple.com>luket...@apple.com
>>>
>>
>
>
> --
> <http://ericd.net>http://ericd.net
> Interactive design and development
>
>
--
http://ericd.net
Interactive design and development
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
