{"shas":[["74ec1570fe2094f8211809271a2e0d20c55fd2a3","5442e2b64fa09764b9f593867e59a97292c84059@adroit-technologies.com","Creating a ScrollerDefinitionTest to test ScrollerDefinition.  When inspecting this commit, please pay special attention to the changed event names in ScrollerDefinition and ScrollerBehavior.  We are typically naming the property change events using a formula of: property + \"Change\".  However, this was not the case for \"horizontalPosition\" and \"verticalPosition\".  Instead, the events associated with these properties were omitting \"Position\" from the event name.  I changed this in both of these classes for two reasons: 1) To avoid problems with naming assumptions that currently exist in TestBase.   2) General consistency with other properties/events.  It did not appear, from what I saw, that changing the event names caused any issues.  But, if it does, we may want to handle this situation in a different manner.","whitbeck"],["1439c3d1f1e793fc1b70e04af01b21ebfbe33000","5442e2b64fa09764b9f593867e59a97292c84059@adroit-technologies.com","Adding a testSetContentWithVector() test to ScrollerDefinitionTest.  This test uncovered a bug that required changes in ScrollerDefinition.  The “set content(...)” method currently attempts to allow a Vector to be passed to the SimpleCollection constructor (which expects an Array).  I was seeing two issues with this.  First, if I create a Vector and try to pass it to the “set content(...)” method, the Vector type-check (\"value is Vector\") is false, so it actually falls into the “else”.  Second, if you do pass a Vector to the constructor of SimpleCollection, you get a casting exception.  Please take a look at the changes before accepting this commit.","whitbeck"]],"repo":"benstucki/reflex","actor":"benstucki","ref":"refs/heads/master","size":2,"head":"1439c3d1f1e793fc1b70e04af01b21ebfbe33000","actor_gravatar":"e7574723860f9cf42499a56789686aa4","push_id":24796091}