| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
one second is too long in practice; shortening to 500 msec
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
That way warning's 'active' property will be true by the time Service
gets around to deciding whether or not to show an info dialog.
|
|
|
|
|
|
|
| |
No need to keep the pa_operation pointers around for cancel() cleanup in
volume-warning's pulse dtor -- they are automatically destroyed when
closing the context via context -> pdispatch -> unref callbacks.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
before showing the warning dialog, cache the active sink input index
because it might change while the dialog is visible (eg the video player
pausing playback).
|
| |
|
| |
|