material-components/material-components-android

[BottomNavigationView] BottomNavigationView can have only one setOnNavigationItemSelectedListener

Open

#735 建立於 2019年11月5日

在 GitHub 查看
 (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
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Android developmentJavaMaterial Components for Android
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
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.