跳到主要内容

5 篇博文 含有标签「release」

查看所有标签

WhereQ-DOSBox 1.0.0.13: a restored save keeps the time it was made

· 阅读需 6 分钟
WhereQ-DOSBoxWhereQ-DOSBox

"Just now"​

You come back to the game after lunch. You tap the slot that said you saved it five hours ago. The game loads exactly where you left it — the boss, the health bar, the room you were in.

And the slot now says "just now".

The save is the save you made. The game is the game you left. Only the timestamp lies, and it lies in the direction that makes the app feel like it cannot be trusted with the one thing it is supposed to remember.

That is the whole of 1.0.0.13. It is the smallest release I have shipped and the only one where the fix is three lines long.

WhereQ-DOSBox 1.0.0.10: the sound survives the save state

· 阅读需 10 分钟
WhereQ-DOSBoxWhereQ-DOSBox

The music that stayed behind​

You freeze a game in the middle of a fight. The music is loud, the boss is doing something unpleasant, and you put the phone down to answer a message.

You come back two minutes later and load the state.

The fight is exactly where you left it — the sprites, the health bar, the position of the boss, all of it. The music, though, is somewhere else entirely: it was never frozen with the rest of the machine, so it carried on playing while everything else went back. And the beeping that was coming out of the PC speaker is still going on in the background, droning at nobody.

That was 1.0.0.9. The snapshot was very good, and it was missing the sound.

WhereQ-DOSBox 1.0.0.8: save the whole machine, and a Resume button that resumes

· 阅读需 8 分钟
WhereQ-DOSBoxWhereQ-DOSBox

The button that lied​

Two releases ago I gave the launcher a Resume button. It looked like a promise: press it, and you are back in the game you were playing.

It was not. It started the last game from the beginning, every time.

I did not notice it myself, because on my desk the emulator process was still alive — the game had never really stopped, so there was nothing to resume. Then somebody on a phone pressed the button, lost an hour of progress, and told me plainly: the Resume button restarts the game.

They were right, and the fix was not a one-liner. It took a whole-machine snapshot.

WhereQ-DOSBox 1.0.0.9: the keyboard becomes a handheld console

· 阅读需 9 分钟
WhereQ-DOSBoxWhereQ-DOSBox

A compromise, wearing the shape of a keyboard​

The DOS picture is 4:3. A phone in landscape is 20:9. The difference is two black bars, one on each side of the picture, and for two releases those bars were where the keys lived.

They were not bad bars. The arrows went into the inverted T of a real keyboard, the modifiers and the editing keys into the other side, and the picture kept the whole middle of the screen. It worked.

It was also the wrong shape for the thing it was standing in for. A DOS game is played with the left thumb on the arrows and the right thumb on the keys, and every one of those keys was a long way from where a thumb expects it.

WhereQ-DOSBox 1.0.0.7: your own DOS games, a real JIT, and a launcher that fits on a phone

· 阅读需 10 分钟
WhereQ-DOSBoxWhereQ-DOSBox

The emulator was the easy part​

Yesterday I put WhereQ-DOSBox out into the world: a native Android port of DOSBox, the emulator core running as a real libdosbox.so inside an APK.

The announcement made a promise: your own DOS games, on the actual machine in your pocket.

A promise like that is cheap to make with an emulator that boots to a C:\> prompt. It gets expensive the moment someone tries to actually use it — because then the emulator is the smallest part of the problem.

So here is what six releases, v1.0.0.2 through v1.0.0.7, actually fixed.