[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #17076: [Deskbar Applets] Integrate USBDeskbar Deskbar Applet Into Codebase
From:       "Haiku" <trac () haiku-os ! org>
Date:       2021-07-13 17:46:36
Message-ID: 067.bd06f4ba3f57ff3e3961cf21e79b08a6 () haiku-os ! org
[Download RAW message or body]

--==============Y34123716536666020=MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

#17076: [Deskbar Applets] Integrate USBDeskbar Deskbar Applet Into Codebase
-------------------------------+----------------------------
  Reporter:  CodeforEvolution  |      Owner:  nobody
      Type:  task              |     Status:  new
  Priority:  low               |  Milestone:  Unscheduled
 Component:  Applications      |    Version:  R1/Development
Resolution:                    |   Keywords:
Blocked By:                    |   Blocking:
  Platform:  All               |
-------------------------------+----------------------------
Comment (by pulkomandy):

 > The reason this is necessary, is that for our system sounds contest, a
 device connect and disconnect sound was made

 This is not a valid reason. Also, why would these sounds be specific to
 USB? They would be much more useful with bluetooth, for example, where
 there are no wires, and it makes sense to have other ways to know if a
 device is connected or not.

 Moreover, the sounds should be configured through the system wide sound
 preferences and not a specific deskbar applet.

 > can indicate whether a cable is faulty, or if a device simply is not in
 a state where it can talk to Haiku.

 This should be done with error messages, not just sounds.

 > I think of that preflet as more for "advanced users". After all, usb
 devices are very likely connected to the computer externally by an average
 user, and I feel as though having information about those devices easily
 accessible could help an average user determine whether their usb
 connected devices are properly detected and registered with Haiku without
 using command line tools or digging into the Devices preflet which lists
 every internal and external device that Haiku has detected.

 I think it is providing users with informations they don't need in the
 first place. You connect a device, it starts working immediately. You
 don't need to list it or something like that. Unless you are an advanced
 user, of course.
-- 
Ticket URL: <https://dev.haiku-os.org/ticket/17076#comment:3>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
--==============Y34123716536666020==--

[prev in list] [next in list] [prev in thread] [next in thread]