You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered a unique bug, I have a list of say 100 records which the user generates itself, on longpress on a row i show the quick action menus.
Problem is when i scroll once, and if i longpress on 1st showing row after sroll, the quickaction shifts 2 positions below,
When i scroll twice and if i longpress on 1st showing row after sroll, the quickaction shifts say 3 or 4 positions below, that means the quick action menu is shown but below 4 rows that was actually long pressed.
When i long press the last item in my list i.e. the 100th item, since after each scroll the quick action menus shift position, as per your algorithm written in QuickAction.java class, the show() method is called but due to 4-5 scrolls the quickaction menu is way below the last item in the list, which obstructs it from Showing.
I hope you will help me in this .
Thanks,
Varun Thakur.
The text was updated successfully, but these errors were encountered:
Hello,
I have encountered a unique bug, I have a list of say 100 records which the user generates itself, on longpress on a row i show the quick action menus.
Problem is when i scroll once, and if i longpress on 1st showing row after sroll, the quickaction shifts 2 positions below,
When i scroll twice and if i longpress on 1st showing row after sroll, the quickaction shifts say 3 or 4 positions below, that means the quick action menu is shown but below 4 rows that was actually long pressed.
When i long press the last item in my list i.e. the 100th item, since after each scroll the quick action menus shift position, as per your algorithm written in QuickAction.java class, the show() method is called but due to 4-5 scrolls the quickaction menu is way below the last item in the list, which obstructs it from Showing.
I hope you will help me in this .
Thanks,
Varun Thakur.
The text was updated successfully, but these errors were encountered: