summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorJeff Brown <jeffbrown@google.com>2011-10-12 15:41:34 -0700
committerJeff Brown <jeffbrown@google.com>2011-10-12 22:19:41 -0700
commit5e5d6d8ba04d7579df840cda055cd5dfa9d7666f (patch)
treeb9c47baaa3b62795dfc12645da4bed2eb5d3ec13 /include
parent5b2dda3be5cc903aafb77ce7902c14d76eb26a9b (diff)
downloadframeworks_base-5e5d6d8ba04d7579df840cda055cd5dfa9d7666f.zip
frameworks_base-5e5d6d8ba04d7579df840cda055cd5dfa9d7666f.tar.gz
frameworks_base-5e5d6d8ba04d7579df840cda055cd5dfa9d7666f.tar.bz2
Deprecate local-only CursorWindows.
There is no difference and has never really been a difference between local-only and remotable CursorWindows. By removing the distinction officially in the API, we will make it easier to implement CrossProcessCursor correctly. CrossProcessCursor is problematic currently because it's not clear whether a call to getWindow() will return a local-only window or a remotable window. As a result, the bulk cursor adaptor has special case handling for AbstractWindowedCursors vs. ordinary CrossProcessCursors so that it can set a remotable window before the cursor fills it. All these problems go away if we just forget about local-only windows being special in any way. Change-Id: Ie59f517968e33d0ecb239c3c4f60206495e8f376
Diffstat (limited to 'include')
-rw-r--r--include/binder/CursorWindow.h3
1 files changed, 1 insertions, 2 deletions
diff --git a/include/binder/CursorWindow.h b/include/binder/CursorWindow.h
index 5d490ed..f0284de 100644
--- a/include/binder/CursorWindow.h
+++ b/include/binder/CursorWindow.h
@@ -80,8 +80,7 @@ public:
~CursorWindow();
- static status_t create(const String8& name, size_t size, bool localOnly,
- CursorWindow** outCursorWindow);
+ static status_t create(const String8& name, size_t size, CursorWindow** outCursorWindow);
static status_t createFromParcel(Parcel* parcel, CursorWindow** outCursorWindow);
status_t writeToParcel(Parcel* parcel);