[haiku-bugs] Re: [Haiku] #7091: Bluetooth UI layer refactoring and improvement
- From: "yourpalal" <trac@xxxxxxxxxxxx>
- Date: Wed, 12 Jan 2011 17:17:54 -0000
#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:8 oruizdorantes]:
> 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.
>
> Well we could try to change that so that Adding a TAB the class returns
the assigned index or something like that. Will make things less simple in
the server side, having to store all the assigned numbers instead of the
fixed constants
Another option is to pass the view name in place of the index, which
combines the best of both worlds (fixed "handles" + no extra BList). This
also makes it simple to find the view in question using BView::FindView().
All that would be needed on the server side would be to make sure the
string literals are assigned to a const char* somewhere. How does that
sound to you?
--
Ticket URL: <http://dev.haiku-os.org/ticket/7091#comment:11>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
