OSDN Git Service

Camera2/3: Properly disambiguate FPS range vs. single FPS setting
authorEino-Ville Talvala <etalvala@google.com>
Fri, 20 Sep 2013 23:32:26 +0000 (16:32 -0700)
committerEino-Ville Talvala <etalvala@google.com>
Fri, 20 Sep 2013 23:32:26 +0000 (16:32 -0700)
commit70b054021a3a22622c2710267362c5e235ed73bd
tree24341d0e6cc5882b0d105b1bda2969fedcf831f3
parent0181fde7bd20238cb13ae2665f0e5bfe7c2d9ac8
Camera2/3: Properly disambiguate FPS range vs. single FPS setting

The camera1 API allows for either setPreviewFrameRate or
setPreviewFPSRange, so both values may or may not change in a single
setParameter call.

The disambiguation of which setting has been changed since the last
setParameter() call was not fully correct, so a sequence of changes
that only changed setPreviewFPSRange or didn't change either could be
interpreted as as a change to setPreviewFrameRate.

Bug: 10842868
Change-Id: I40baeced80a58f09f8a1742ece8dd5e141e9c1e3
services/camera/libcameraservice/api1/client2/Parameters.cpp
services/camera/libcameraservice/api1/client2/Parameters.h