[BottomNavigationView] BottomNavigationView can have only one setOnNavigationItemSelectedListener · material-components/material-components-android#735

(3 评论) (8 反应) (0 负责人)Java (15,910 star) (3,023 fork)batch import

Good First IssueWidget: BottomNavigationfeature request

描述

FEATURE REQUEST

As per title, BottomNavigationView can have only one setOnNavigationItemSelectedListener. This is annoying because if i use the bottomNavigationView.setupWithNavController(navController) this internally sets that listener, and i cannot use it anymore for anything else (like setting the text in a custom appBar, for example) A list of listeners would be the right thing in my opinion.

Ps. this probably applies to setOnNavigationItemReselectedListener(BottomNavigationView.OnNavigationItemReselectedListener listener) too.

For Pattern reference, see NavController addOnDestinationChangedListener and removeOnDestinationChangedListener

贡献者指南

技术栈: javaandroid
领域: mobiledesign
议题类型: feature
难度: 3
预计时间: half day
活动状态: stale
清晰度: clear
前置要求: Android developmentJavaMaterial Components for Android
新手友好度: 40
研究方向: The issue requests allowing multiple listeners on BottomNavigationView instead of a single one. The recommended approach is to follow the pattern used by NavController's addOnDestinationChangedListener/removeOnDestinationChangedListener, which maintains a list of listeners. To implement, locate the BottomNavigationView class (likely in the library source code) and modify it to store a list of OnNavigationItemSelectedListener instances, then iterate over them when an item is selected. Ensure backward compatibility by keeping the single setter method but adapting it to the new list. No linked PRs or recent comments provide additional direction.