#7091: Bluetooth UI layer refactoring and improvement -------------------------------------------+------------------------------ Reporter: hamish | Owner: yourpalal Type: enhancement | Status: assigned Priority: normal | Milestone: R1 Component: Network & Internet/Bluetooth | Version: R1/Development Resolution: | Keywords: Blocked By: | Has a Patch: 1 Platform: All | Blocking: -------------------------------------------+------------------------------ Comment (by yourpalal): Replying to [comment:4 hamish]: > I believe fOutputViewsList is still needed. When the other Bluetooth modules add tabs to the output window, they supply their own arbitrary constant as an identifier for the tab, and this constant doesn't neccessarily match up to the view's index on the tab view, so it needs to be stored. Yes, actually, I just looked around a bit and I think you are right. Its sort of a strange way of doing things, but alas. So, fOutputViewsList can stay, but I would still like to see the _OutputViewAt() method used in Output::MessageReceived(). I think though, in light of this new info, _OutputViewAt() should be call _OutputViewForTab(), or something similar. -- Ticket URL: <http://dev.haiku-os.org/ticket/7091#comment:5> Haiku <http://dev.haiku-os.org> Haiku - the operating system.