Timing issues among registered callbacks (where is the exact frame boundary)

Quest79 / snes9x-rr

Automatically exported from code.google.com/p/snes9x-rr

0 stars 1 forks source link

Timing issues among registered callbacks (where is the exact frame boundary) #25

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

At present, there can be some emulations between emu.registerafter (and
gui.register) and emu.registerbefore. That causes 1 frame delay to RAM
display for certain RAM values.

Original issue reported on code.google.com by gochaism on 18 Nov 2009 at 8:22

GoogleCodeExporter commented 9 years ago

Original comment by gochaism on 18 Nov 2009 at 8:22

Changed title: Timing issues among registered callbacks
Added labels: ****
Removed labels: ****

GoogleCodeExporter commented 9 years ago

Original comment by gochaism on 18 Nov 2009 at 8:23

Changed title: Timing issues among registered callbacks (where is the exact frame boundary)
Added labels: ****
Removed labels: ****