tobiasvl / love-8 Goto Github PK

love-imgui?

Not sure if this is a duplicate of #2 or not.

Things to think about:

• Fetch and execute more than one opcode at a time
• Make sure timers tick down at ~60 Hz
• Lock FPS? (See above)

Create separate display modules that alter screen resolution and effects.

• VIP
• HP48

• Break on unknown opcode
• Breakpoints
• Break on V access/change
• Break on memory write/read

Options:

• Follow PC
• Disassembly
• Jump to
• Breakpoint

mattmikolay/chip-8#3

This thing runs really slowly.

I want to make a test ROM that doesn't simply test for SCHIP compatibility (like all the existing ones do?) but classifies your compatibility.

Don't draw everything to the screen each frame, that's probably pretty slow (see #2). Instead, draw to a canvas whenever the screen data changes, and draw the canvas to the screen each frame.

According to Wikipedia, FX1E should set VF to 1 if it results in I overflowing from FFF (not FFFF?)

• Get rid of globals
• Create CPU object, and probably others
• Split into multiple files

Native File Dialog?

Aka. "quirks"

Add Super-CHIP instructions