summaryrefslogtreecommitdiff
path: root/src/com/android/mail/ui/ConversationCursorLoader.java
Commit message (Collapse)AuthorAgeFilesLines
* Revert "UnifiedEmail: Supported Email search function"Danny Baumann2016-12-301-5/+0
| | | | | | This reverts commit ad4f76791d5306f6046150cefd7de07d9d15aa33. Change-Id: I396973b7f27a5df483a7845b16b1db804bb8916b
* UnifiedEmail: Supported Email search functionweitan2016-08-241-0/+5
| | | | | | | | | | | | | | | | | | | 1. Use the search function to search the local mail. 2. Search results interface: Filters All, Subject, Sender, Receiver click on the different filter, and search the corresponding results. All for the default selection filter. 3. Search results interface: slide switch filter, remove "sliding removing a single mail" effect. 4. Search results interface: alternative condition, slide switch filter, cancel the multiselect state. 5. Search results interface: UI-filters layout, sliding effect, search, according to the number of search results highlighted. Change-Id: I2af40a386de55e221878bd346cda3ea1cff8f2fa CRs-Fixed: 1023498
* Allowing overriding conversation list load limit.Andrew Sapperstein2014-04-011-4/+4
| | | | | | | | | | | | b/7280077 One issue we saw was that if the conversation was not in the initial 50 conversations, we would get punted out of the conversation list. Now we have an additional extra in ACTION_VIEW intents that allow ignoring the limit for the first load of the ConversationCursor. Change-Id: I737c45e122df4dda7c63794ddc7036be61d5ebd4
* Unify LogTagScott Kennedy2013-06-051-8/+8
| | | | | | | | | | | | | | | | | | | | There is now only one LogTag class. The static initializer of GmailApplication (existing) and EmailApplication (new) will now set the log tag to "Gmail" and "Email", respectively. Up until that code is run, it will be "UnifiedEmail". "setprop log.tag.Gmail VERBOSE" (or .Email) will trigger all logs to be printed as long as they go through LogUtils, regardless of what tag is used by that individual log. This lets us still turn on logging everywhere in one command, but also lets us use more descriptive tags (like the class name). And since we no longer have three com.android.mail.utils.LogTag classes, builds will be much easier. Also, we now use LogUtils everywhere. Change-Id: Iec53e87cad0a46b73d2afbbd8d44aca097a5087a
* CleanupScott Kennedy2013-04-051-1/+1
| | | | Change-Id: Iee8abf75639450d469632e43fe0e102b687558db
* Hide conversations from list after removal via notif actionScott Kennedy2013-02-221-1/+1
| | | | | | | | | If a conversation is archived, deleted, or has a label removed via a notification action, we should hide it from the conversation list until either the undo notification is activated, or it times out. Bug: 8248145 Change-Id: Ib88a14142238b5553f80d59e67be5f64ab2a28fb
* Resolve all STOPSHIP comments in UnifiedEmailVikram Aggarwal2013-02-151-1/+1
| | | | | | | | | Bug 8211088 filed for the remaining case. Bug: 8132946 Investigate the STOPSHIP comment in EmailProvider.java wrt PII Change-Id: I0f93e7bd68360eccbf781c144addf8a8a66ae779
* Remove activity leakVikram Aggarwal2013-01-031-15/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | The conversation cursor was maintaining a static reference to loaders and the resolver. When the cursor was loaded immediately after orientation changes, the CursorLoader framework returns the existing cursor. This cursor contained the reference to the old activity. This also meant that the sResolver reference was stale till the conversation cursor was recreated. As suggested by ath@, we remove the static ContentResolver, and rely on a member. Also, as suggested by ath@, we use the ApplicationContext, which removes the inner memory leak that was being caused by the CursorWrapper holding on to a context, which held on to the previous application. Just one activity on rotate (after GC). Also contains minor code cleanup: removing unused import and cleaning up incorrect javadoc on methods. Bug: 7883592 mild activity leak Change-Id: I09043c38055e5d7ed2fb345286b1f293e39bf4c3
* Fix resetting ConversationCursorPaul Westbrook2012-08-171-6/+1
| | | | | | | | | | | | | | | We need to reset the state of the Activity controller when the ConversationCursor is reset. It isn't necessary for ConversationCursorLoader to call the callback's onReset, as this will happen from the loader manager Also, the loader manager only calls onLoaderReset() if the caller has valid data from a new instance of the loader, but onReset of the loader is still called. We don't want to call onLoaderReset() for every call to onReset() Bug: 7009556 Change-Id: If943409028aa8f5e465a5dba4bac1307a4d4e0fe
* Fix some problems with conversation cursorPaul Westbrook2012-08-011-1/+0
| | | | | | | | | | | | | 1) If someone called setCursor, the internal state of the ConversationCursor would prevent new cursors from being observed 2) If onRefreshReady happend while the list is scrolling, that wasn't handled when the list scrolling stopped 3) If both onRefreshReady and onRefreshRequired happened while the list is scrolling, when the list stopped scrolling, only onRefreshRequired would be called, which ends up unregistering the observer Change-Id: I1b07b8b41b1025b981f5fdae7d6e2e18568029de
* Make sure reset ConversationCursorLoader gets cleaned upMarc Blank2012-08-011-1/+9
| | | | | Bug: 6381692 Change-Id: I4a427d0076f790091d4d166b10c322e1844f5003
* Fix broken logging of loader add/removeMarc Blank2012-07-201-1/+1
| | | | Change-Id: Ib53a26d548ddc13b24c14ef4d501453697b1b8a5
* Major refactor of ConversationCursorPaul Westbrook2012-04-201-12/+88
| | | | | | | | | | | | | * ConversationCursors are now associated with a particular loader; there are no static methods or static state fields * ConversationCursorLoader maintains a list of current loaders (for tracking/debugging) * AbstractActivityController acts as a router of conversation changes to/from fragments (currently message view -> conversation list) * Comment out some ConversationCursor tests for now Change-Id: I9b8425a19c77501796b6681142e1bc0ad20b3693
* Revert "Major refactor of ConversationCursor"Marc Blank2012-04-201-88/+12
| | | | This reverts commit 5150f03723af8019169aeed8e406784da9c5f8f1.
* Major refactor of ConversationCursorPaul Westbrook2012-04-201-12/+88
| | | | | | | | | | | | * ConversationCursors are now associated with a particular loader; there are no static methods or static state fields * ConversationCursorLoader maintains a list of current loaders (for tracking/debugging) * AbstractActivityController acts as a router of conversation changes to/from fragments (currently message view -> conversation list) Change-Id: I0eb554615b4bf93b3547ff28e2bd5913e8703a97
* Comment out pause/resumeMarc Blank2012-04-181-2/+2
| | | | Change-Id: Id96c69a9924f05e7c2129984176be293aad1aced
* Don't stop loading onReset for CCMarc Blank2012-04-161-5/+0
| | | | | Bug: 6345560 Change-Id: I2c8c31d9da507f47919817760916bc4132ce6459
* Lots 'o ConversationCursor goodnessMarc Blank2012-04-161-0/+2
| | | | | | | | * Throttling the cursor! * Almost dead list items! * But wait! There's more! Change-Id: If0fe7b3d22e2dfa0e1d7bb2eaa307d20c52dc21c
* Add "limit" to first load of ConversationCursorMarc Blank2012-03-201-7/+12
| | | | | | | | * For my large convo list, time for first query is down to about 300ms from average 9000ms * TODO: Clean all this up... Change-Id: Iaa17f5b8b5b773cb4c8133b4f22d7096b3a3aa54
* Allow a Conversation to be created with just the conversationPaul Westbrook2012-03-161-0/+3
| | | | | | | | fields Work around for NPE when marking conversation as read before ConvrsationCursor is created Change-Id: I495d408146287de5d6ce7253d2e082cc4d4b4d6a
* Store URI's in Uri instead of String.Mindy Pereira2012-02-281-2/+2
| | | | Change-Id: I5492a61b80442afc7cebc5b3d560688aebae8820
* Get loading folders/conversations off the ui thread.Mindy Pereira2012-02-161-0/+59
Use loaders. Pretty. Change-Id: I0d87ffa8e390f15718c71f05977ff6d331aeb9ca
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-16 18:30:19 +0000