path: root/sub/osd_dummy.c
diff options
authorwm4 <wm4@nowhere>2014-01-18 01:19:20 +0100
committerwm4 <wm4@nowhere>2014-01-18 01:27:43 +0100
commit7f4a09bb8534dfafd83099d773adf2e33c64e267 (patch)
tree5b75791151f92e164fbd9badee47590d1164683d /sub/osd_dummy.c
parent92a9f11a0b4fda60c8880014be5920dcf3e95253 (diff)
sub: uglify OSD code path with locking
Do two things: 1. add locking to struct osd_state 2. make struct osd_state opaque While 1. is somewhat simple, 2. is quite horrible. Lots of code accesses lots of osd_state (and osd_object) members. To make sure everything is accessed synchronously, I prefer making osd_state opaque, even if it means adding pretty dumb accessors. All of this is meant to allow running VO in their own threads. Eventually, VOs will request OSD on their own, which means osd_state will be accessed from foreign threads.
Diffstat (limited to 'sub/osd_dummy.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/sub/osd_dummy.c b/sub/osd_dummy.c
index cc2ba37377..6fc78ab368 100644
--- a/sub/osd_dummy.c
+++ b/sub/osd_dummy.c
@@ -24,7 +24,7 @@ void osd_object_get_bitmaps(struct osd_state *osd, struct osd_object *obj,
*out_imgs = (struct sub_bitmaps) {0};
-void osd_object_get_resolution(struct osd_state *osd, struct osd_object *obj,
+void osd_object_get_resolution(struct osd_state *osd, int obj,
int *out_w, int *out_h)
*out_w = 0;