Shell Command Patch, v0.3

picture

Shell Command Patch

This update to the Shell Command Patch improves security by limiting where the patch can be used.

For more information on this update, email info@kineme.net.

[ More info on this patch ]
Universal Binary

AttachmentSize
ShellCommandPatch-0.3.zip14.51 KB
ShellCommandPatch-0.3-src.zip55.76 KB

being a "renderer"...

...ie a pink patch means it can only exist in a macro without any outputs, which is kinda annoying as most of the use i have for this is as a data mangling node, away from the actual rendering macros. is there any chance of this being worked-around, or is this the only way to force it to execute on input change?

cwright pictureinitially

Initially, I made it a renderer because that's the only way to make it execute without it needing to be attached to a renderer.

I can build a non-renderer one (with the implied condition being that'll only execute when attached to a renderer somehow) if you'd like.

yanomano pictureKB shotcuts from shell command ?

Is there a way to output keyboard shortuts from terminal, and/or from the shell command patch ?
Is there another way to generate this from QC ?

regards.

yanomano.

cwright pictureoascript

Keyboard shortcuts are high-level events, I don't think shell stuff can induce that directly (without some special programs that inject artificial events onto the event queue).

However, you can call a program called "oascript", which can run an apple script. AppleScripts can probably cause most of the functionality of shortcut keys, so that might be a direction to investigate.