SuperCard Changelog

What's new in SuperCard 4.7.3

Dec 2, 2011
  • A maintenance release that is provided free of charge to all registered users of SuperCard 4.7.
  • This release addresses compatibility with Lion, and is recommended for all users of SuperCard 4.7.

New in SuperCard 4.7.2 (Jul 25, 2011)

  • A maintenance release that is provided free of charge to all registered users of SuperCard 4.7.
  • This release addresses compatibility with Lion, and is recommended for all users of SuperCard 4.7.

New in SuperCard 4.7.1 (Mar 15, 2011)

  • Addresses a number of issues that could cause unexpected behavior in your projects. It also includes a few new features as well. It is recommended for all users of SuperCard 4.7.
  • For information about changes and additions in this release please see the Release Notes file in the SuperCard 4.71 folder of the disk image.
  • To receive the update simply complete the form at left and you should receive an email from us within the hour with download information.

New in SuperCard 4.6.3 v2 (Jun 20, 2008)

  • Version 4.6.3v2 corrects an issue with Standalone Maker 4.6.3.

New in SuperCard 4.6.3 (May 16, 2008)

  • The following externals have been added to Xtend
  • fontMetrics
  • The following externals have been updated in Xtend
  • dragRect
  • flash
  • getIconDataFromFile
  • getResources
  • For more information on the above externals please see the Xtend window in the SuperCard Help System.
  • The following changes have been made to the Internals Toolbox
  • GetObjectInfo and GetObjectInfoByIndex have been updated so that they correctly report the allowObjects property setting in 4.6x projects.
  • weInsertObject has been updated so it correctly handles raw image data in non-PICT formats.
  • The IT Xcode templates have been modified to add a compile flag which prevents generation of constant CFStrings. Apparently these can cause mysterious crashes after the owning project is closed if they have been passed to (and retained by) various Cocoa-based Toolbox APIs (Cocoa assumes executable bundles will never be unloaded).