diff options
| author | wm4 <wm4@nowhere> | 2012-08-31 18:08:47 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2012-09-07 16:06:32 +0200 |
| commit | 914c8dc577ef782d8e350d9a5d68657108d04c19 (patch) | |
| tree | 74d88a24bcd49d2cf2eef5279cf0d47876653384 /osdep | |
| parent | cafa00841fc1d0515a2063e7c64d884ad2019658 (diff) | |
| download | mpv-914c8dc577ef782d8e350d9a5d68657108d04c19.tar.bz2 mpv-914c8dc577ef782d8e350d9a5d68657108d04c19.tar.xz | |
osd: reset OSD progression display
The code for showing OSD progression ('P' key) set a flag in a
mp_osd_msg_t to do its work. OSD messages can be re-used for completely
unrelated purposes (it's unclear why), so this has to be reset if an
old OSD progression message is reused for something different.
Be sure to reset the full message. Remove the messy code for searching
the OSD stack. Use the existing rm_osd_msg() function to remove the old
message (if there was one), and always create a new message. The new
code should be functionally equivalent to the old code. The "started"
flag wasn't reset before, but since the time is always overwritten, this
might be actually more correct.
Diffstat (limited to 'osdep')
0 files changed, 0 insertions, 0 deletions