mirror of
https://github.com/InvisibleUp/uvmac.git
synced 2024-11-28 15:50:11 +00:00
1 line
16 KiB
HTML
1 line
16 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title> Changes in Mini vMac 3.1.3 </title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="canonical" href="v3.1.html">
</head>
<body>
<div>
<i> <a href="https://www.gryphel.com/index.html">www.gryphel.com</a>/c/<a href="../index.html">minivmac</a>/<a href="index.html">change</a>/v3.1
- <a href="https://www.gryphel.com/c/feedback.html">feedback</a> </i>
</div>
<hr>
<h3 align=center>
Mini vMac 3.1.3
</h3>
<h3 align=center>
Changes
</h3>
<hr>
<p> What has changed in Mini vMac 3.1.3, compared to Mini vMac 3.0.4.
This only lists changes that affect behavior, and so doesn't
include cleanups of the source code. </p>
<p> : </p>
<p>
default compile:
</p>
<blockquote>
<p>
<a href="v3.1.html#feature">New features</a>
</p><p>
<a href="v3.1.html#modified">Changed behavior</a>
</p><p>
<a href="v3.1.html#bugs">Bug fixes</a>
</p>
</blockquote>
<p>
not in default compile:
</p>
<blockquote>
<p>
<a href="v3.1.html#compile_feature">New features</a>
</p><p>
<a href="v3.1.html#compile_modified">Changed behavior</a>
</p><p>
<a href="v3.1.html#compile_bugs">Bug fixes</a>
</p>
</blockquote>
<p>
<a href="v3.1.html#build">Build System</a>
</p>
<p> : </p>
<p> <a name="feature"> <b> New features in default compile </b> </a> </p>
<p> * If Mini vMac, on Mac OS X or Windows, doesn't find the
<a href="../hardware.html#rom">ROM</a>
file in the folder containing the application, it will now
also look in a specific central location. In OS X it
checks in "/Users/[your_UserName]/Library/Preferences/Gryphel/mnvm_rom/".
In Windows XP, "C:\Documents and Settings\[your_UserName]\Application Data\Gryphel\mnvm_rom\".
Windows 98, "C:\WINDOWS\Application Data\Gryphel\mnvm_rom\". And
in Vista, I think "C:\Users\[your_UserName]\AppData\Roaming\Gryphel\mnvm_rom\".
Usually "mnvm_rom" would be an alias (on OS X, on Windows this is called a short cut)
to where ever you keep your ROM collection.
This avoids having to create an alias to the ROM image
for each emulated Mac you use. </p>
<p> <a name="modified"> <b> Changed behavior in default compile </b> </a> </p>
<p> * The alternate CPU emulation of Mini vMac 3.0.4 is now the main and only emulation.
(The “-alt-cpu” build option is gone.) This makes Mini vMac slightly
faster, and allows more accurate detection of illegal instructions without
speed penalty. It also reduces the amount of code to be optimized in
assembly language (Currently only done for PowerPC).
The PowerPC assembly code version has been revised to match the new emulation,
and is now used for the PowerPC Linux version. </p>
<p> * More accurate mouse and keyboard event handling, by using an event
queue to communicate between the platform dependent code and the platform
independent code. Previously, the platform dependent code would tell
the platform independent code every emulated sixtieth of a second the
current mouse position and up/down state of the mouse button and keys.
If the host computer was very busy, or just slow, then a down and up
pair could end up being processed in the same emulated sixtieth, and
they would cancel each other out and be lost entirely. Also a mouse
button state change might not be processed until well after it happened,
and the mouse position might be different by then.
(Though if Mini vMac is not getting time every sixtieth of a second,
so that these problems can be observed, then sound emulation isn't
likely to work either, emitting horrible noises. But it is possible
to compile Mini vMac without sound. And also if the host computer
is a device without a keyboard, such as using handwriting recognition,
then there might not be separate key down and key up.) </p>
<p> * The Macintosh and Windows versions now match the X version in
not initially filling the sound buffer with silence, but
instead waiting to accumulate real sound samples before starting
to play sound. This may reduce the tendency to stutter
as
|