First of all, I am trying to achieve high compatibility by emulating all components cycle accurately. The execution thread is organized as an infinite loop.The VirtualC64 project is based on three major goals. You can register the listener any time, even to a running emulator.Īt the time the listener is registered, all pending messages are automatically sent to the registered callback. Best c64 mac emulator code#If you use the core emulator in a different environment and do not want register a callback, you can periodically query the queue with code similar to the following Objective-C example code. In the current implementation, a Swift closure is registered that processes all incoming messages. At launch, the GUI will register a callback function that is invoked whenever a new message is written into the queue. To communicate with the GUI, the emulator writes messages into a message queue. This function starts the execution thread and brings the emulator to life. The GUI reacts to this message by calling run. Commodore - 64 Emulators - Zophar's Domain Dirk Hoffmann, VirtualC64 talks back via a message queue that triggers a callback function whenever a message is written into the queue. Please note that I don't want to port the emulator to another operating system at the moment. If you can identify with these goals, I would be happy to actively participate in this project. Thirdly, I am trying to create a well-documented and understandable code base. In addition to achieving a high level of compatibility, I want to create a user interface that is as easy to use as possible. Best c64 mac emulator how to#
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |