mikeboers
mikeboers
About Me
Connect
LOCATION
Not Specified
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Bypass floating expression editor April 25, 2012, 5:59 p.m.
Howdy!
I'm trying to sort out some usability issues with respect to external script editors on the Mac.
When I press opt-e in a parmeter, I get the Houdini expression editor. Pressing opt-e again will open up my external $EDITOR, however the original Houdini expression editor floats above my external editor despite the “Keep Floating Windows on Top” setting.
Is there a way to either stop the Houdini expression editor from floating on top, or directly jump to an external editor (bypassing the Houdini editor entirely)? Or perhaps is it possible to get access to the current parameter from inside of a shelf tool when triggered via a keyboard shortcut?
Cheers!
Mike
I'm trying to sort out some usability issues with respect to external script editors on the Mac.
When I press opt-e in a parmeter, I get the Houdini expression editor. Pressing opt-e again will open up my external $EDITOR, however the original Houdini expression editor floats above my external editor despite the “Keep Floating Windows on Top” setting.
Is there a way to either stop the Houdini expression editor from floating on top, or directly jump to an external editor (bypassing the Houdini editor entirely)? Or perhaps is it possible to get access to the current parameter from inside of a shelf tool when triggered via a keyboard shortcut?
Cheers!
Mike
License Server Woes Aug. 12, 2011, 1:17 p.m.
I have been having exactly the same issue. Every time I open Houdini it opens the License Administrator instead and prompts to install the licenses. If I open the License Administrator directly it will show existing apprentice licenses…
It has been like this for a few days. I keep trying newer and newer daily build, but it never works.
It has been like this for a few days. I keep trying newer and newer daily build, but it never works.
File CHOP can't open audio on OS X May 30, 2010, 10:19 p.m.
Whenever I try to open an audio file (aiff or wav) using a File CHOP on OS X I get the error:
Unable to read file “(null)”.
Unable to read file “<actual path here>”.
I got around it by writing a script to convert my .aiff into a .bclip, but feels like it should have been unnecessary. =P
Any ideas?
Unable to read file “(null)”.
Unable to read file “<actual path here>”.
I got around it by writing a script to convert my .aiff into a .bclip, but feels like it should have been unnecessary. =P
Any ideas?