From: Rich W. <rj...@he...> - 2001-11-29 16:14:53
|
On Thursday 29 Nov 2001 3:51 pm, Miguel Freitas wrote: > i forgot to cc xine-dev, this might be useful for someone else... Indeed it was. Just a small quation; below is the trace from my latest=20 attempts to get highlighting to work. These events are sent just at a sce= ne=20 change (jump). As you can see, since there is no frame being shown betwee= n=20 the events, they are both queued and then executed together. The problem = is=20 that the are executed in the reverse order to which they were called (i.e= =2E=20 the hide event is processed before the last show event). Is this a bug in my code or the new OSD stuff? Rich dvdnav_plugin_read_block: Highlight area is (426,145)-(526,350), display = =3D 1 MALLOC1: overlay_event (nil), len=3D4 MALLOC2: overlay_event 0x82dce08, len=3D4 MALLOC1: overlay (nil), len=3D128 MALLOC2: overlay 0x82dce30, len=3D128 BUTTON show=3D1 clut [0 0 0 0] trans [48 100 9 64] left =3D 426 right =3D 526 top =3D 145 bottom =3D 350 dvdnav_plugin_read_block: FIXME: VTS change dvdnav_plugin_read_block: Highlight area is (37156,16505)-(63488,16548),=20 display =3D 0 MALLOC1: overlay_event (nil), len=3D4 MALLOC2: overlay_event 0x82dcf40, len=3D4 MALLOC1: overlay (nil), len=3D128 MALLOC2: overlay 0x82dcf68, len=3D128 BUTTON show=3D0 clut [0 0 0 0] trans [48 100 9 64] left =3D 0 right =3D 0 top =3D 0 bottom =3D 0 dvdnav_plugin_read_block: FIXME: Cell change video_overlay: HIDE MENU NOW 0 MENU BUTTON NOW video_overlay: error: button event received and no overlay allocated. Segmentation fault --=20 Rich You need no longer worry about the future. This time tomorrow you'll be = dead. |