Well, this only exists because of the first issue as you note.

jpr: should I add an Exit button to the right click menu?

[ I still don't think this is an issue, because we don't ship a launcher for nm-applet anywhere (right?) and thus the user can only start more than one instance via the command line. ]

Its up to you, I consider this not necessary for Code 10.

I will say that it seems strange to exit something in the notification area since its supposed to be notifying you of some event anyhow.

I added it, along with a neat option to disable the autostart mechanism.

Committed to CVS and submitted to autobuild as 0.6.0cvs20060307.

UI review has actually demanded that this functionality be removed, as it is confusing to the user.

Marking WONTFIX.  The proper way to disable NetworkManager is via YaST (the applet will not appear if the daemon is disabled).

so the only way to disable the applet is to disable the hole NetworkManager?!
I would like to have the ability to close applets I don't wanna use, even without disabling the service behind them.

In what scenarios would you like to use NM but not use the applet?  The only one I can think of is if you want to use only ethernet (one card only) and don't want to access connection info or VPN or disable networking on the fly.

Note, you can also disable this from gnome-session-properties in the startup section.

Christian: Believe me, I agree with you.  The consensus is that you can disable the applet via gnome-session-properties or manually via the autostart files.  But the argument was made that very few users (and no non-advanced users) would want to remove the applet but keep the NetworkManager service running, and thus the presence of the Remove option is confusing.

Ok, I have just thougt about the case that someone could, not why, so I don't have any scenarios.

Robert: So the possibillity is there for deactivating? That's all I wanted to notice.

Christian: Yup, gnome-session-properties will let you disable any of the autorun stuff.