Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Jeff Parsons ed75397b83 Fixed an old annoying bug where a restored video card wouldn't properly display a blinking cursor; originally, I assumed it was a CRTC register restoration bug, but actually, some supporting variables (eg, cBlinks) were not getting initialized in both the reset() and restore() code paths. This is also a good time to remember that when an uninitialized array from some hardware state gets serialized and deserialized to/from JSON, the array is restored as a series of "null" values, not as "undefined" values, so it's best for any code checking for undefined values to use "== null" rather than "=== undefined".		2017-06-26 08:56:17 -07:00
..
common.css	Started work on v1.35.1	2017-06-21 11:18:02 -07:00
common.xsl	Got rid of more app-specific demo machines (eg, DONKEY and WIN101); demos like that are more properly located in either the /apps or /disks folders (not /devices)	2017-06-22 12:03:52 -07:00
components.css	Started work on v1.35.1	2017-06-21 11:18:02 -07:00
components.xsl	Got rid of more app-specific demo machines (eg, DONKEY and WIN101); demos like that are more properly located in either the /apps or /disks folders (not /devices)	2017-06-22 12:03:52 -07:00
document.css	Started work on v1.35.1	2017-06-21 11:18:02 -07:00
document.xsl	Started work on v1.35.1	2017-06-21 11:18:02 -07:00
machine.xsl	Started work on v1.35.1	2017-06-21 11:18:02 -07:00
manifest.xsl	Started work on v1.35.1	2017-06-21 11:18:02 -07:00
outline.xsl	Started work on v1.35.1	2017-06-21 11:18:02 -07:00
pcx86-dbg.js	Fixed an old annoying bug where a restored video card wouldn't properly display a blinking cursor; originally, I assumed it was a CRTC register restoration bug, but actually, some supporting variables (eg, cBlinks) were not getting initialized in both the reset() and restore() code paths. This is also a good time to remember that when an uninitialized array from some hardware state gets serialized and deserialized to/from JSON, the array is restored as a series of "null" values, not as "undefined" values, so it's best for any code checking for undefined values to use "== null" rather than "=== undefined".	2017-06-26 08:56:17 -07:00
pcx86-dbg.map	Fixed an old annoying bug where a restored video card wouldn't properly display a blinking cursor; originally, I assumed it was a CRTC register restoration bug, but actually, some supporting variables (eg, cBlinks) were not getting initialized in both the reset() and restore() code paths. This is also a good time to remember that when an uninitialized array from some hardware state gets serialized and deserialized to/from JSON, the array is restored as a series of "null" values, not as "undefined" values, so it's best for any code checking for undefined values to use "== null" rather than "=== undefined".	2017-06-26 08:56:17 -07:00
pcx86-uncompiled.js	Fixed an old annoying bug where a restored video card wouldn't properly display a blinking cursor; originally, I assumed it was a CRTC register restoration bug, but actually, some supporting variables (eg, cBlinks) were not getting initialized in both the reset() and restore() code paths. This is also a good time to remember that when an uninitialized array from some hardware state gets serialized and deserialized to/from JSON, the array is restored as a series of "null" values, not as "undefined" values, so it's best for any code checking for undefined values to use "== null" rather than "=== undefined".	2017-06-26 08:56:17 -07:00
pcx86.js	Fixed an old annoying bug where a restored video card wouldn't properly display a blinking cursor; originally, I assumed it was a CRTC register restoration bug, but actually, some supporting variables (eg, cBlinks) were not getting initialized in both the reset() and restore() code paths. This is also a good time to remember that when an uninitialized array from some hardware state gets serialized and deserialized to/from JSON, the array is restored as a series of "null" values, not as "undefined" values, so it's best for any code checking for undefined values to use "== null" rather than "=== undefined".	2017-06-26 08:56:17 -07:00
pcx86.map	Fixed an old annoying bug where a restored video card wouldn't properly display a blinking cursor; originally, I assumed it was a CRTC register restoration bug, but actually, some supporting variables (eg, cBlinks) were not getting initialized in both the reset() and restore() code paths. This is also a good time to remember that when an uninitialized array from some hardware state gets serialized and deserialized to/from JSON, the array is restored as a series of "null" values, not as "undefined" values, so it's best for any code checking for undefined values to use "== null" rather than "=== undefined".	2017-06-26 08:56:17 -07:00