title: Multiple sticky objects of the same class?
body: <p>I'm using sticky events in EventBus to pass my "selected" objects into the upcoming Activity. The detail activity allows the user to "select" another object to fetch a new list. I want to post another sticky event with the <em>same</em> object class again into yet another list activity, but from what I understand, the previous sticky will get overwritten. See the example illustration at the bottom.</p>
  
  <p>What is the recommend way around this problem? I need to have n-nested sticky events with the same class in EventBus.</p>
  
  <p>I really like having sticky objects, it eliminated my need to hand-wire up the Android Parcelable interface just to send objects from one living activity to another with the <code>Intent</code> mechanism. I'd hate to be forced to go and have to implement Parcelable even after getting a fully working EventBus just because I can't have nested sticky objects!</p>
  
  <p>One way I thought up was to maintain my own stack of <code>Item</code> objects in an ArrayList in a Singleton, pushing when diving deeper (before startActivity) and popping when backing out (but where? <code>onDestroy</code> is not to be used), but the approach seems extremely fragile to me. I need a robust mechanism - this is the primary navigation pivot for my app.</p>
  
  <ul>
  <li>List of items, user selects an <code>Item</code>. We post a sticky event with this <code>Item</code> and startActivity with detail view class in Intent.</li>
  <li>User browses through the detail and asks for a list of related items. We start another activity showing the list.</li>
  <li>User selects an <code>Item</code>.  We post a sticky event with this <strong>second</strong> <code>Item</code> and startActivity with detail view class in Intent. The second <code>Item</code> overwrites the first <code>Item</code> and when the user wants to navigate up the back stack, it is no longer available to read, instead the last sticky item created is read.</li>
  </ul>