> > I talked to Tanu and Arun last week about my what-did-you-plugin-dialog, > and got some push back about my way of popping up the dialog. > > So, instead, what do you think of this solution - does this provide a > good separation between PulseAudio and the GUI process: > > * The dialog will be popped up through DBus activation. We define some > DBus name, e g org.pulseaudio.WhatDidYouPlugIn - and when accessing this > name, the process will be started by DBus. > * There will be DBus methods for popping up and killing the dialog, and > a signal back when the user selects something in the dialog (or cancels it). > > Second, we will create a new pulseaudio sub-project, pa_popup_dialogs or > something. This will contain the current dialog (it's designed by > Canonical, but it's nothing Ubuntu specific about it), and our > recommended solution by upstream. If gnome, kde, or some other DE wants > to write their own themed dialog, they will just install their own > solution instead, which we will communicate with through the > org.pulseaudio.WhatDidYouPlugIn name/interface. (I have some test code > using zenity too, but that will be dropped.) > Is this one time setup or user have to select everytime when they plugged or reboot ? Once setup, use are unlikely to change this setting until they buy another headset/headphone Can this popular dialog be disabled ?