Click or drag to resize

MultiplePrefabsExample Class

Example implementation demonstrating the use of 2 different views holders, representing 2 different models into their own prefab, with a common Title property, displayed in a Text found on both prefabs.

The only constrain is for the models to have a common ancestor class and for the views holders to also have a common ancestor class

Also, the BidirectionalModel is used to demonstrate how the data can flow from the model to the views, but also from the views to the model (i.e. this model updates when the user changes the value of its corresponding slider)

At the core, everything's the same as in other example implementations, so if something's not clear, check them (SimpleExample is a good start)

Inheritance Hierarchy
SystemObject
  Object
    Component
      Behaviour
        MonoBehaviour
          Com.ForbiddenByte.OSA.CoreOSAMyParams, BaseVH
            Com.ForbiddenByte.OSA.Demos.MultiplePrefabsMultiplePrefabsExample

Namespace:  Com.ForbiddenByte.OSA.Demos.MultiplePrefabs
Assembly:  Assembly-CSharp (in Assembly-CSharp.dll) Version: 0.0.0.0
Syntax
C#
Copy
public class MultiplePrefabsExample : OSA<MyParams, BaseVH>, 
	ExpandCollapseOnClickISizeChangesHandler

The MultiplePrefabsExample type exposes the following members.

Constructors
  NameDescription
Public methodMultiplePrefabsExample
Top
Properties
  NameDescription
Public propertyData
Top
Methods
  NameDescription
Public methodChangeItemsCount

Self-explanatory. See ItemCountChangeMode in order to understand how change modes differ from each other.

Every count change operation (Refresh(Boolean, Boolean), InsertItems(Int32, Int32, Boolean, Boolean) etc.) ultimately calls this method, so it's a good place for example to fire a custom "ItemsChanged" event, if you need to

(Overrides OSATParams, TItemViewsHolderChangeItemsCount(ItemCountChangeMode, Int32, Int32, Boolean, Boolean).)
Protected methodCreateViewsHolder
Creates either a BidirectionalVH or a ExpandableVH, depending on the type of the model at index itemIndex. Calls Init(RectTransform, Int32, Boolean, Boolean) on it, which instantiates the prefab etc.
(Overrides OSATParams, TItemViewsHolderCreateViewsHolder(Int32).)
Protected methodIsRecyclable
Overriding the base implementation, which always returns true. In this case, a views holder is recyclable only if its CanPresentModelType(Type) returns true for the model at index indexOfItemThatWillBecomeVisible
(Overrides OSATParams, TItemViewsHolderIsRecyclable(TItemViewsHolder, Int32, Double).)
Public methodOnExpandedStateChanged
Protected methodOnItemIndexChangedDueInsertOrRemove

This is overidden only so that the items' title will be updated to reflect its new index in case of Insert/Remove, because the index is not stored in the model

If you don't store/care about the index of each item, you can omit this

For more info, see OnItemIndexChangedDueInsertOrRemove(TItemViewsHolder, Int32, Boolean, Int32)

(Overrides OSATParams, TItemViewsHolderOnItemIndexChangedDueInsertOrRemove(TItemViewsHolder, Int32, Boolean, Int32).)
Protected methodStart (Overrides OSATParams, TItemViewsHolderStart.)
Protected methodUpdateViewsHolder

Here the data in your model should be bound to the views. Use newOrRecycled.ItemIndex (ItemIndex) to retrieve its associated model

Note that views holders are re-used (this is the main purpose of this adapter), so a views holder's views will contain data from its previously associated model and if,

for example, you're downloading an image to be set as an icon, it makes sense to first clear the previous one (and probably temporarily replace it with a generic "Loading" image)

Note that this is not called for items that will remain visible after an Insert or Remove operation is done

(Overrides OSATParams, TItemViewsHolderUpdateViewsHolder(TItemViewsHolder).)
Top
Version Information

Optimized ScrollView Adapter

Supported in: 4.1
See Also