Select particular position of dot about dotsindicator

[tommybuonomo]

Hi @akankshapaul048 ,
If you call setCurrentItem() on your ViewPager, the dots will automatically refresh

[akankshapaul048]

Well i did that but no changes

[edChori]

Try this
Handler().postDelayed({viewPager.setCurrentItem(1, true)}, 100)

[wachidsusilo]

@SamadiPour This worked for me:

    private void buildViewPager(){
        ....
        viewPager.setCurrentItem(0); //this goes to onCreate() method
    }

    private boolean onStart = true;
    @Override
    public void onWindowFocusChanged(boolean hasFocus) {
        if(onStart){
            onStart = false;
            viewPager.setCurrentItem(initialPosition, false); //set initial position you want
        }
    }

[oliverspryn]

Correct, this is still a problem, unless you setCurrentItem with an animation.

viewPager.setCurrentItem(1, true)

[vkotovv]

@tommybuonomo any updates on this?

[SamadiPour]

Handler().postDelayed({viewPager.setCurrentItem(1, true)}, 75) worked but i want it without this!
is there any other way?

[krodyrobi]

Hello, we've hit this as well.

Both the Spring and Worm implementations have the same buggy behavior, on a dark mode switch it selects the 1'st dot but the adapter reports position 3 as the currently active item.
It does not happen on the Dots one, and that is a shame as Worm is so cool.

Debugging the override fun onPageScrolled(selectedPosition: Int, nextPosition: Int, positionOffset: Float) callback of worm we see the correct nextPosition but since the dots are not present (only 1 is rendered) it cannot compute the offset to scroll to.

vp.setCurrentItem(pos, smooth) only works correctly for Dots not for the other 2.
In our case we use flow and no matter the delay we use we cannot get it to work.

Dot state recovers on next / prev page navigations or on adapter changes.
Can you guys have a look at it?

[AntonShynkaretskyi]

It's still the problem. Indicator doesn't update it's state correctly, and I don't see a way to set currentItem manually

[tommybuonomo]

Duplicate of #126

[tommybuonomo]

Hello there, thanks everyone for your contribution
This will be fixed in the 4.3 release