- When a savestate is done, should I include the current joypad data / shifting? Is this really required when a savestate is loaded?
- I did a quick optimization here, but it might fail on saves:
- It replaces the usual code:
- What do you think about it?
- I did a quick optimization here, but it might fail on saves:
Code:
-pseudo-code-
value = joypad_read << 1;
-then, on 4016/7 reads:
value >>= 1;
return value & 1;-
value = joypad_read << 1;
-then, on 4016/7 reads:
value >>= 1;
return value & 1;-
- It replaces the usual code:
Code:
-pseudo-code-
value = joypad_read;
-then, on 4016/7 reads:
unsigned char temp = value & 1;
value >>= 1;
return temp;
value = joypad_read;
-then, on 4016/7 reads:
unsigned char temp = value & 1;
value >>= 1;
return temp;
- What do you think about it?