Something is weird in the design of gpilotd-control-applet, the inventor
may speak his/her mind in response of this, but the idea to bring up a
basic controller (identifying devices etc) with

gpilotd-control-applet

without any command-line options, and to have the same applet bring up the
conduit interface with the command line option:

gpilotd-control-applet --cap-id=1

is not good, not intuituitive. Notably RedHat has broken their distribution
so that it is impossible to access the conduits from the menus, and also
Ximian evolution has a problem that is probably related.

My proposed solution to this is: by all means, keep that command-line
option if you like it, but PLEASE PLEASE add the conduits as a tab to the
interface of the dialog that is brought up when invoking
gpilotd-control-applet without any options. You often want to configure all
things at once, see, you might want to be able to configure conduits apart
from the rest (though I doubt it) but you ALWAYS want to configure conduits
at the same time you use the other configure options.

I am ready to create a patch for you if you accept this idea and don't have
the time to do it yourself.

This controller-applet behaviour has already caused severe problems for
users who don't realize the "obvious" idea of launching
"gpilotd-control-applet --cap-id=1" with that totally undocumented (am I
wrong?) switch.

Atleaste give me good reasons for why the controller-applet is built this way.