#Vice emulator mac pdf#
#Vice emulator mac update#
#Vice emulator mac Pc#
#Vice emulator mac windows#

Even if we could remove the per frame scanning from the emulator itself, the operating system and last not least the keyboard itself would still impose a certain limit (something like 10ms for USB HID keyboards, for example). This comes from the fact that the keyboard is (and can not) be scanned in real time (ie every 1mhz cycle).

When typing very quickly, some keypresses might get lost.

F2 = Shift + F1, F4 = Shift + F3 and so on) this also works with other keys. Note: also see this knowledgebase article Workaround: If you have to use the function keys, press the (real) shift key manually (e.g. at the same clock cycle) with the main key this could not work with some keyboard routines.

#Vice emulator mac Pc#

When a key which is shifted on the real machine but unshifted on the PC or Unix keyboard you are using is pressed, the virtual shift is pressed together (i.e.x128 does not autostart prg files correctly when also a cartridge is attached (that forces c64 mode).xplus4 gives 'sound buffer overrun' on autostart with certain settings (which settings?).autostart seems to be broken in xcbm2 and xcbm5x0 at least with the settings the testbench wants to use.TODO: make a test program to determine the type of delay line used for a PAL screen (UV or U only).TODO: make a test program to determine visible screen dimensions.TODO: fix the reference screenshots and/or the scripts so they dont rely on the 'normal' rendering mode anymore.many test programs (mostly for vic20) are not yet integrated into the automatic testing.descriptions of several snapshot modules are missing (Plus4, TED.)ДЇor details look at doc/Documentation-Howto.txt.some descriptions of emulator formats are missing (D67, D1M, D2M, D4M.).

some info that was previously hidden in target specific articles on the VICE knowledge base should get merged into vice.texi - the remaining articles are here.

The documentation is partly outdated and/or incomplete, in particular:

#Vice emulator mac pdf#

pdf documentation, which is exported correctly.

many nodes are not yet linked correctly, which makes some of the exporters output garbled and/or suboptimal output (unix.

#Vice emulator mac update#

TODO: Remove the 'dither' column from the palette files and update the code accordingly.

#Vice emulator mac windows#

replace readline and our fallback implementation with linenoise ( ), or perhaps linenoise-ng ( ) which appears to support Windows and UTF-8.

TODO: get rid of fullscreenarch.h and fullscreen.c - its no more required because both SDL and GTK3 can do all of the features fine.

Resource_and_Cmdline_checking - Tracks and documents all Resources and Command line options.

revisit the old Feature checking pages, and clear it out eventually.

remove the third scaling method described in Scaling_cleanup (formerly used by XAW) (fixed?).

remove compiler- and platform- specific hacks (IFDEFS) in common code.

Code cleanup and streamliningДЄs of 3.2 we started removing a lot of the old cruft, that was dangling around in the tree for way too long, to make maintenance easier Generally regressions are not acceptable and respective commits are subject to be reverted. Do not commit deal breaking changes without communicating it with the rest of the team. Please at least test the issue you were trying to fix before committing. Only remove a bug/feature from this list when it was fixed/implemented in the latest stable release.

After fixing a bug or implementing a new feature, update its status on the Bug Tracker and mark it as fixed in the TODO list below.

When adding/changing command-line options and/or resources, adding a new feature or change the behavior of an existing feature, please update the documentation.

When adding/changing stuff that needs (G)UI items/changes, all developers should update the SDL and GTK3 UIs themselves, and immediately following their respective changes.

Document your code so other people than you are able to understand and fix it in a decade or two.

All developers shall subscribe to the vice-emu-mail mailinglist and perhaps join #vice-dev on freenode too (highly recommended).

7.2.1 UI code refactoring to support the new threaded UI code.