GNOME Bugzilla – Bug 598386
bluetooth-wizard: set discoverability
Last modified: 2009-10-15 11:02:50 UTC
It would be a good thing if bluetooth-wizard allowed to set the visibility of the own machine; f.i. like the following: * automatic PIN code selection * use fixed PIN code * initiate pairing from out of the bluetooth device checkbox: make my computer visible to other bluetooth devices If 'initiate pairing from out of the bluetooth device' is selected the visibility-checkbox should automatically be marked.
Why would you want to do that? Note that you can already set the visibility of the computer through the preferences (bluetooth-properties)
That does not help me because I want to use bluetooth-wizard as standalone application for the Xfce and KDE3 desktops. No bluetooth-properties tray icon in these environments!
.
The properties aren't an applet.
The properties for the panel applet won`t help as Xfce and KDE3 don`t have a panel that is compatible with Gnome. My request is to make bluetooth-wizard usable as standalone app. It is such a nice application!
(In reply to comment #5) > The properties for the panel applet won`t help as Xfce and KDE3 don`t have a > panel that is compatible with Gnome. The properties is a stand-alone program. > My request is to make bluetooth-wizard usable as standalone app. It is such a > nice application! Not going to happen, it's built to work along with the rest of the applications.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 598385 ***
As you have already indicated for Bug 598385 I would simply let bluetooth-properties be invoked by bluetooth-wizard. That would resolve this issue as well. It would perhaps also be good to mention that there is an alternative way to do things in the intro of bluetooth-wizard or by an own radio-button: set your computer discoverable and initiate the pairing by the mobile bluetooth device. A good wizard always has an intro, doesn`t it?
(In reply to comment #8) > As you have already indicated for Bug 598385 I would simply let > bluetooth-properties be invoked by bluetooth-wizard. That would resolve this > issue as well. Except that you still didn't tell me a single reason why you should do that. > It would perhaps also be good to mention that there is an alternative way to > do things in the intro of bluetooth-wizard or by an own radio-button: set your > computer discoverable and initiate the pairing by the mobile bluetooth device. > A good wizard always has an intro, doesn`t it? Why would you want to do that? And explaining that you need to make your computer discoverable would be mentioned in the manual for your device anyway. Also, that wouldn't solve your problem, if the applet isn't running, you won't have any ways to do the pairing on the computer side...
> bluetooth-properties be invoked by bluetooth-wizard I thought we would agree on this in Bug 598385, Comment 10 > Why would you want to do that? point out an alternative way if it shouldn`t work the other way round. users may not think of it - and they do not read manuals. > if the applet isn't running, you won't have any ways to do the pairing on the computer side Perhaps even bluetooth-wizard could invoke bluetooth-applet or better a more simple program like passkey-agent or simple-agent if the user selects 'initiate pairing from the phone' and bluetooth-applet does not run already
(In reply to comment #10) > > bluetooth-properties be invoked by bluetooth-wizard > I thought we would agree on this in Bug 598385, Comment 10 No. The only way to access the wizard is through: - the applet (which should have a discoverable menu entry, see bug 573955) - the properties/preferences window, which already has the ability for you to change the discoverability > > Why would you want to do that? > point out an alternative way if it shouldn`t work the other way round. > users may not think of it - and they do not read manuals. Yes, and they use the UI. You're running bluetooth-wizard from the command-line, so you should know how to launch the other properties. Furthermore the wizard is made to initiate pairing *from* the computer. Being discoverable is only useful to pair from the phone. > > if the applet isn't running, you won't have any ways to do the pairing on the computer side > Perhaps even bluetooth-wizard could invoke bluetooth-applet or better a more > simple program like passkey-agent or simple-agent if the user selects 'initiate > pairing from the phone' and bluetooth-applet does not run already No, because the wizard is to initiate pairing *from* the computer, and the applet is used to initiate pairing *to* the computer.
Implement what you like. These are my recommendations. Otherwise you may receive further bug reports of users who don`t get along with things as they are now.