Difference between revisions of "Talk:Bluetooth Passthrough"

From Dolphin Emulator Wiki
Jump to: navigation, search
 
(One intermediate revision by one other user not shown)
Line 7: Line 7:
  
 
:I think those all sound like good ideas. I don't see a problem with any of that. My only idea is to label the rest of the columns with hover-over descriptions like the VID/PID have so it's obvious what the possible answers should be, to keep everything tidy. (Or a little clickable question mark/number instead, so that the hover-over descriptions can be read on mobile.) - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 21:15, 15 December 2019 (CET)
 
:I think those all sound like good ideas. I don't see a problem with any of that. My only idea is to label the rest of the columns with hover-over descriptions like the VID/PID have so it's obvious what the possible answers should be, to keep everything tidy. (Or a little clickable question mark/number instead, so that the hover-over descriptions can be read on mobile.) - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 21:15, 15 December 2019 (CET)
 +
 +
:: It's somewhat half-way done, ended having more columns than I expected. I was considering making another column for the chipset used and decouple that from the adapter name (currently listed under [] on the adapter name) but I think I'm crossing the line and going way too technical. Any thoughts before continuing? Any feedback on the added columns? [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 21:51, 18 December 2019 (CET)
 +
 +
:::Another column isn't a big deal to add in my opinion since removing the range column and adding in the type and BT columns added up to the same width, and adding another chipset column would still be just as wide afterwards anyways. But it looks good the way it is too with the chipset in brackets, so it's really whatever you want. I think it looks really good so far. - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 00:28, 19 December 2019 (CET)

Latest revision as of 01:28, 19 December 2019

Adapter Test Results refactoring

So, apart from small additions here and there, the adapter test results haven't received any meaningful update for some years. I have plans to at least partially address that, but before continuing, I really think we should completely drop the range column: it didn't turn out how we planned and I strongly think it has no meaningful significance for the reader (e.g. how far "Long" or "Very Long" actually is? Does it account for obstacles or other interferences?).

The audio column, on the other hand, still is relevant, but I think we should limit the allowed values to either ? (not tested), No (doesn't work or has major issues), Limited (works but has small issues on specific conditions -- e.g. multiple Wiimotes playing audio simultaneously) or Yes (works the same or better than the Wii Bluetooth module), just like the existing columns.

And finally, I would like to add a new column telling if the adapter in question is a standalone USB adapter or if it's the Bluetooth portion of a WiFi Card. Could be as simple as a "Type" column where the two allowed options are USB or PCIe. Thoughts? mbc07 (talk) 00:09, 14 December 2019 (CET)

I think those all sound like good ideas. I don't see a problem with any of that. My only idea is to label the rest of the columns with hover-over descriptions like the VID/PID have so it's obvious what the possible answers should be, to keep everything tidy. (Or a little clickable question mark/number instead, so that the hover-over descriptions can be read on mobile.) - Xerxes (talk) 21:15, 15 December 2019 (CET)
It's somewhat half-way done, ended having more columns than I expected. I was considering making another column for the chipset used and decouple that from the adapter name (currently listed under [] on the adapter name) but I think I'm crossing the line and going way too technical. Any thoughts before continuing? Any feedback on the added columns? mbc07 (talk) 21:51, 18 December 2019 (CET)
Another column isn't a big deal to add in my opinion since removing the range column and adding in the type and BT columns added up to the same width, and adding another chipset column would still be just as wide afterwards anyways. But it looks good the way it is too with the chipset in brackets, so it's really whatever you want. I think it looks really good so far. - Xerxes (talk) 00:28, 19 December 2019 (CET)