| 9ea7077cea45d719026934d33b9deecf4c2eca93 |
|
07-Jan-2015 |
Shri Borde <shri@google.com> |
Bug 18864683: Accessibility
The actionbar is made to stay visibile if accessibility is enabled. This
allows the user to explore and access the menu buttons without it auto-hiding.
The photo details are announced whenever switching to a new photo.
The root view of photo_activity_view is removed from touch exploration as
no actions can be performed by touching it.
Change-Id: I9090920e2154cd9f038d2bede0e4ec9399becc3d
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|
| 05f451df7677dce766b4e6b30ff89e2d3bb0b104 |
|
28-Oct-2014 |
Shri Borde <shri@google.com> |
Bug 16879455: setScaleAnimation() results in RuntimeException
We were destroying the initial thumbnail photo loader as soon as it had
loaded. This recycles the associated bitmap, but that bitmap is used
by mTemporaryImage. The loader is now destroyed only when mTemporaryImage
is being hidden.
Also, a new activity theme has been added with a transparent background.
Change-Id: Icdc39581e8b0b609617465be56217961494322da
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|
| 55ac8ea9519e981bfdbd83c82615c72cfa78d84c |
|
19-Aug-2014 |
Shri Borde <shri@google.com> |
Bug 16879455: PhotoViewFragment.sPhotoSize initialized late
The NPE happens because PhotoViewFragment.sPhotoSize is null. It is
initialized in PhotoViewFragment.sPhotoSize. However, PhotoBitmapLoader is
created from Activity.onCreate. The fix moves the initilization to
PhotoBitmapLoader.
Change-Id: I125115a6882df9c1c8c7e1325068958b7cdfc468
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|
| f39584b0cd6b5cd47a76854efffe437366693b3e |
|
04-Aug-2014 |
George Ruban <gruban@google.com> |
Search for uri from beginning of data instead of wherever
the cursor happens to be at the time.
BUG: 16654182
Change-Id: I6e6e9bd56b17997c0d02b329e992614a5be665fd
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|
| cd95597f2dfc0760a105a87d16664e56ca1a4afe |
|
12-Jun-2014 |
Andrew Sapperstein <asapperstein@google.com> |
Additional changes to support controller refactor.
Change-Id: Ia06983da92e562a51e47644f9cf9cf1c3fe30c79
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|
| bb137c8e2ed363e6f5e2c0f14719483d27e8c062 |
|
05-Jun-2014 |
Mathew Inwood <mathewi@google.com> |
Move all logic from activity into controller.
Get rid of ControllerCallbacks, and instead create a thin wrapper around
Activity exposing the functionality required from the activity. Do the same
for ActionBar to take care of android.support.v7.app.ActionBar and
android.app.ActionBar (which have an identical interface).
This eliminates a lot of duplicate code between the appcompat activity and
the other activity. The only duplicated code is not boring wrapper code.
To customize the activity now, subclass PhotoViewController and implement
customizations in there. Then subclass the Activity and override
createController to instantiate your controller subclass.
Also allow subclassing of PhotoViewFragment. This is to enable the fragment
to replace the logic of getting the controller from the activity, in the
instance that the activity does not implement ActivityInterface directly
itself.
Bug: 15090270
Change-Id: Ib31ae155b5afabff848624b0721d6eaf96312c12
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|
| 90382f446827fc956839b6294fb13dda6040583c |
|
06-Mar-2014 |
Adam Copp <adamcopp@google.com> |
Disable immersive mode on tablets before L.
this works around a bug in the platform that locks all input to the
device if a secondary user is active when an app enters immersive mode.
Bug: 13233844
Change-Id: I34ac3461702931411621856bf4614f1edde898c4
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|
| f5a30690749a354cbbf8c8d9ad4fd5ed84e7d41e |
|
23-Oct-2013 |
Matt Keoshkerian <mattak@google.com> |
Use SYSTEM_UI_FLAG_FULLSCREEN for all uses of lights out mode in JellyBean.
Janky animations are avoided by setting the correct layout flags for clients using scale animation.
Needed for b/8173898
Change-Id: Idad94c30c471e86abd392f1e94b1bd762129157e
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|
| e9825b89f8d8a61c747c5dc8aeaac9004a07d755 |
|
23-Oct-2013 |
Matt Keoshkerian <mattak@google.com> |
Fix crashing in GB when entering photoviewer
Two issues:
1. View.OnSystemUiChangeListener was introduced in API level 11.
2. getActionBar() was used instead of getSupportActionBar() in appcompat
Related to b/10804270 and b/9534809
Change-Id: Ie9b5369ad2f61785597fb711babea29426078929
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|
| 1b641422773c48c8fe4f3b6bc6570f7e098124f2 |
|
22-Oct-2013 |
Matt Keoshkerian <mattak@google.com> |
Delay calls to setting lights out until after enter animation completes
This will only happen if mScaleAnimation is enabled. Calls to setting lights out causes an animation, which gets janky when it animates concurrently with the scale animation.
Fix for b/8173898
Change-Id: I05f768b9e7d6991930f968d5adb2b91b2efcfb7c
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|
| 5f0775af25a40843a2c68d67d694945d88514555 |
|
12-Oct-2013 |
Andrew Sapperstein <asapperstein@google.com> |
Immersive mode.
Fixes b/10804270 and b/9534809.
Also starts creating a controller to
consolidate duplicate PhotoViewActivity implementations.
Change-Id: I9b4dae9a017f23bfd9e170177e74289ae8ce475b
/frameworks/opt/photoviewer/src/com/android/ex/photo/PhotoViewController.java
|