Problems with new daily builds and scrollView setIsLocked?

As folks here who use Corona’s widget library may recall, a daily build about two weeks ago (2014.2481) introduced a lot of changes. One of those is listed as:

Widgets - scrollview widget lock (by adding setIsLocked(BOOL trueFalse, [String direction] (“horizontal” or “vertical")) - casenum 32845 

Since that daily build I haven’t been able to lock a scrollview after initial creation. I’ve tried :setIsLocked(true), :setIsLocked(true, “horizontal”), and, just in case, :setIsLocked(true, (“horizontal”)). None of those work for me.

The line in the daily build release says a new string parameter has been added to the :setIsLocked method, but the documentation hasn’t been updated yet: http://docs.coronalabs.com/api/type/ScrollViewWidget/setIsLocked.html

Can Rob or someone else from Corona help me out here? How do we lock scrollviews after creation using daily builds from the last two weeks?

Also posted in daily builds here: http://forums.coronalabs.com/topic/52604-problems-with-new-daily-builds-and-scrollview-setislocked/

I just ran a quick test:

        scrollView:setIsLocked( true )
        scrollView:setIsLocked( false )
        scrollView:setIsLocked( false, “horizontal” )
        scrollView:setIsLocked( false, “vertical” )

        scrollView:setIsLocked( true, “horizontal” )
        scrollView:setIsLocked( true, “vertical” )

with 2496 and everything worked as expected.

Rob

Thanks, Rob, for your help and sorry to bother you. Looks like user error! Now to find out where the problem lies…

Also posted in daily builds here: http://forums.coronalabs.com/topic/52604-problems-with-new-daily-builds-and-scrollview-setislocked/

I just ran a quick test:

        scrollView:setIsLocked( true )
        scrollView:setIsLocked( false )
        scrollView:setIsLocked( false, “horizontal” )
        scrollView:setIsLocked( false, “vertical” )

        scrollView:setIsLocked( true, “horizontal” )
        scrollView:setIsLocked( true, “vertical” )

with 2496 and everything worked as expected.

Rob

Thanks, Rob, for your help and sorry to bother you. Looks like user error! Now to find out where the problem lies…