yes, you are right, but thie bug is about the applet that does not update itself when there is that dbus command.
this means that network-manager changes its status the applet does not recognize this, this is the problem I was pointing at if an application exposes a dbus command, everyone can use it (for instance inside a bash script), and every piece of the application must be synced with oters: it does not make sense that if in the network manager daemon wireless is disabled, in the applet we see it enabled, but not working (because the daemon has it disabled)... ----- Messaggio originale ----- Da: Bastien Nocera <[EMAIL PROTECTED]> A: yelo_3 <[EMAIL PROTECTED]> Cc: network manager <[email protected]> Inviato: Mercoledì 23 maggio 2007, 0:29:51 Oggetto: Re: blocking bug for laptop users On Tue, 2007-05-22 at 20:03 +0000, yelo_3 wrote: > it is blocking because people using a hotkey to switch of/off > wireless, will see a different status in the applet: > - the hotkey toggles wireless using the dbus method setWirelessEnabled > - the applet does not update itself, so the user who disables > wireless, will see in the applet that wireless is enabled, and the > exact list of wireless network that were active before he had hit the > hotkey That's not the right way to do it, especially as some "hotkeys" act directly on the hardware. The correct way to do it is: - have HAL do get/set on the hardware (either using custom APIs for each models, like already implemented for Dells, or the generic kernel rfkill API) - Make NetworkManager handle the get/set from the hardware -- Bastien Nocera <[EMAIL PROTECTED]> ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
