This occurred to me when I downloaded the latest release, which has
changed the default screen dimensions.
I believe that phones with 'portrait' screens generally change to a
'landscape' orientation when the user is operating the camera, since
users expect the greatest area of the screen to operate as a
viewfinder. I know for certain that the N95 operates in this way, and
I would expect that other phones do too.
Given this scenario, these phones must have their cameras embedded
orthogonally to their screen orientation. Of course these orientations
may be somewhat nominal, but the issue remains that developers need to
know these relative orientations so that their applications can
sensibly project camera input to the screen.
(A related issue which perhaps constitutes a separate RFE is that I
can't see a way of influencing the desired screen orientation - say
when the user wants to use the camera, or when a sensor indicates a
change in physical orientation. There appear to be ORIENTATION
constants on Surface, but I can't seem to piece together a sequence of
API calls to use them within the View system.)
tomgibara wrote: > This occurred to me when I downloaded the latest release, which has > changed the default screen dimensions.
> I believe that phones with 'portrait' screens generally change to a > 'landscape' orientation when the user is operating the camera, since > users expect the greatest area of the screen to operate as a > viewfinder. I know for certain that the N95 operates in this way, and > I would expect that other phones do too.
> Given this scenario, these phones must have their cameras embedded > orthogonally to their screen orientation. Of course these orientations > may be somewhat nominal, but the issue remains that developers need to > know these relative orientations so that their applications can > sensibly project camera input to the screen.
> (A related issue which perhaps constitutes a separate RFE is that I > can't see a way of influencing the desired screen orientation - say > when the user wants to use the camera, or when a sensor indicates a > change in physical orientation. There appear to be ORIENTATION > constants on Surface, but I can't seem to piece together a sequence of > API calls to use them within the View system.)
> tomgibara wrote:
> > This occurred to me when I downloaded the latest release, which has
> > changed the default screen dimensions.
> > I believe that phones with 'portrait' screens generally change to a
> > 'landscape' orientation when the user is operating the camera, since
> > users expect the greatest area of the screen to operate as a
> > viewfinder. I know for certain that the N95 operates in this way, and
> > I would expect that other phones do too.
> > Given this scenario, these phones must have their cameras embedded
> > orthogonally to their screen orientation. Of course these orientations
> > may be somewhat nominal, but the issue remains that developers need to
> > know these relative orientations so that their applications can
> > sensibly project camera input to the screen.
> > (A related issue which perhaps constitutes a separate RFE is that I
> > can't see a way of influencing the desired screen orientation - say
> > when the user wants to use the camera, or when a sensor indicates a
> > change in physical orientation. There appear to be ORIENTATION
> > constants on Surface, but I can't seem to piece together a sequence of
> > API calls to use them within the View system.)
I just tried using the window service in this way from the onCreate of
an activity. It worked to a degree, all rendering was rotated ninety
degrees, but somewhat amusingly none of the view components had
adjusted to their new screen coordinates for input purposes.
Incidentally, if this screen rotation becomes a standard fixture of
the API (which I think it must ultimately) then the emulator will need
to rotate its display too to 'save our necks'.
On Dec 17, 9:55 pm, Davanum Srinivas <dava...@gmail.com> wrote:
> tomgibara wrote:
> > This occurred to me when I downloaded the latest release, which has
> > changed the default screen dimensions.
> > I believe that phones with 'portrait' screens generally change to a
> > 'landscape' orientation when the user is operating the camera, since
> > users expect the greatest area of the screen to operate as a
> > viewfinder. I know for certain that the N95 operates in this way, and
> > I would expect that other phones do too.
> > Given this scenario, these phones must have their cameras embedded
> > orthogonally to their screen orientation. Of course these orientations
> > may be somewhat nominal, but the issue remains that developers need to
> > know these relative orientations so that their applications can
> > sensibly project camera input to the screen.
> > (A related issue which perhaps constitutes a separate RFE is that I
> > can't see a way of influencing the desired screen orientation - say
> > when the user wants to use the camera, or when a sensor indicates a
> > change in physical orientation. There appear to be ORIENTATION
> > constants on Surface, but I can't seem to piece together a sequence of
> > API calls to use them within the View system.)
