10.5

This update to GLTools adds a few small new features.

First, the Spline patch now allows you to render points at each subdivision (not just each control point).

Second, the Polygon Mode patch now allows you to enable/disable point and line smoothing, as well as line stipple control.

Unsurprisingly, another Intel GL bug was uncovered: Enabling point-smoothing in polygon-mode mode results in no output. Yay lame intel drivers...

[ yanomano should have some really cool pictures to show for these requests... ;) ]

This update to the SerialIO patch addresses a bunch of bugs with the serial input patch. Break String stuff now works.

It has been tested with our arduino board for simple reception, and appears to handle it well. It's likely for issues to still exist, but now we're in a position to test a bit, so development on this can proceed with more ease than earlier this year.

QCRehab gives some of the unofficial-API functionality back to the Official API. Features such as Safe Mode and Subpatch support are enabled, allowing more flexible plugins.

This plugin uses the Unofficial API, so it goes in ~/Library/Graphics/Quartz Composer Patches/, not ~/Library/Graphics/Quartz Composer Plug-Ins/.

This plugin was written in response to several complaints about 3^rd party plugins not working in "safe" environments. When installed, this plugin will allow all official-api plugins to load in any environment -- This is Extremely Dangerous, Don't Do It Unless You Know You Need it!

For security reasons, it's Disabled in Safari (so malicious compositions cannot harm your machine via the web, even when this plugin is active). Custom plugins should still work in Keynote presentations, in Motion, in Quick Time, and in other applications that may struggle with safe-mode issues.

Note that this does not unlock "unsafe" built-in patches, such as Audio and Video Input. Only custom, Official-API Plug-In patches are unlocked.

It's also useful for plugin developers who are interested in sticking with the official API. It would also be necessary for a user of such plugins.

This plugins obsoletes the "Official API Subpatch Support Plugin" we released a few months ago. It offers identical functionality, including fixed subpatch-save support (meaning compositions with subpatches are properly restored when loaded).

To use this in your Official-API plugins, simply add a +(BOOL)allowsSubpatches method that returns YES to allow subpatches in your patch.

For developers: When making a sub-patch-aware patch, you'll need this piece of code to execute subpatches:[[self patch] executeSubpatches:(double)time arguments:(NSDictionary*)args]. This should go in your execute method only.

Have a lot of fun :)

I expect Apple to include this functionality in a future release of QC, so Please only use this if you know what you're doing. If you bundle this in with other plugins, please make the user aware of what's going on, and how they can remove it.

This beta includes a couple tweaks and fixes. Nothing major.

Checkerboard bug was fixed.

IR output no longer outputs -100 when it looses tracking; instead it retains its last value. You can use the IR structure values to detect tracking loss (since it returns nan's when it loses tracking).

No stability/reliability changes took place.

This beta's pretty rad. It adds a few new features, and a couple powerful patches.

The glOrtho patch now allows you to disable ortho mode (so you can switch from ortho to perspective mode without duplicating all the rendering in your composition).

But the coolest part of all is the GL Point Structure and GL Line Structure Patches. These patches allow you to render collections of points, line segments, or a continuous line strip without the overhead of an iterator.

Both patches take the same structure format: a substructure for each point, with an X, Y, and Z value. If the substructures are keyed, the keys "X", "Y", and "Z" are used, otherwise the 0th, 1st, and 2nd structure members are used to derive the coordinate. I'll probably upload some sample compositions to better demonstrate tomorrow morning.

Using JS to drive it is still slower than molasses, but it's an improvement none the less ;)

Before things get too crazy with structures, I'd like to have a plan in place to duplicate the functionality of vvvv's spreads (these are how this sort of stuff should be solved, not by more structure hacks....)