|
Rosetta repair Shortly after we posted the news item last month about benchmarks running Magic Dice on an Intel Core Duo based Mac vs. an iMac G5, we received some followup feedback from the MacBook Pro owner pointing out an issue in Magic Dice running under Rosetta. All graphics in the application were displayed with solid white rectangles behind them rather than smoothly masked to the background as they appear on PowerPC-based Macs. Thanks to this information and our friends at Solutions Etcetera we now have a fix for this issue which has been built into the latest version of Framework and Magic Dice. This fix has resolved all issues we are currently aware of specifically related to running our software on Intel-based Macs. If anyone finds any further issues with our software running under Rosetta, please let us know. Fixes and improvements Our invitation last month for Magic Dice users to try out the built-in benchmarks for themselves to see how their results compared to our MacBook Pro vs. iMac G5 comparison turned up another interesting bug in our application framework. A couple of users sent us feedback that showed their attempts to search for the word "shareware" as we had done, but that search turned up no results for them while in our tests, 3 matching items were quickly found in the help system. After some additional communication with the users, we discovered this was due to an issue with accented and/or option characters in the path they were running the application from. The latest versions of Framework and Magic Dice fix this issue. We also had a few people send us a copy of their usage logs with benchmark info via the built-in feedback interface in Magic Dice... but they neglected to mention what processor they were running Magic Dice on (and didn't provide any email address for us to contact them). So while we were poking around inside Framework, we also added a brand new function to record the processor type and speed to the usage log. To round off our usage log improvements we also decided to record the underlying foundation and Framework version and build data. Finally, we updated some older resources in Framework and in Magic Dice we improved some of the usage log reporting during game play and activated a benchmark for the time it takes to display score options after each roll of the dice. |
March 2006: |
|||
 |
|
|
|
|
