| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
| |
It looks like these switch statements are intended for future expansion,
so leaving the basic switching logic intact
|
| |
|
| |
|
|
|
|
|
|
| |
After being moved into a class named "VolumeWarning", the high_volume_
prefix was redunant.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
| |
|