2 Replies Latest reply: Nov 21, 2010 10:39 AM by david van brink RSS

    Effect "string" parameter...

    david van brink Community Member

      Oh, I bet it's in one of the samples... but how do you create a String parameter?

       

      (Actually, it's worse: What I really want is a File Path, ideally relative to the Project File. But I know how it is. I'll settle for a String parameter.)

       

      Ideally, it would be Expression-capable, like the Text Layer field is. But if necessary, it can be modal like the old Basic Text and Path Text effects.

       

      Any tips appreciated! thx

        • 1. Re: Effect "string" parameter...
          shachar carmi Community Member

          hello david.

          the reason you didn't find such a param is because there is none.

          what you see in effects like "basic text" is actually an os level window with standard text controls.

          most effects that do that use the "options" button (which can be renamed), to launch the os level window.

          you can also create a param with a custom UI to which AE will send you mouse click events, from which you could launch that window.

           

          another solution would be to create a param with a custom UI, which you can get to act like a string input param (not going to be easy).

           

          the last solution i can think of is to use either the "options" button or a custom param UI to launch a java script (AEGP_ExecuteScript), which will in turn, launch a window with a text control.

          for a simple task like you describe, that might be the easiest way.

          • 2. Re: Effect "string" parameter...
            david van brink Community Member

            Hi Shachar --

             

            Thanks for the notes. (I didn't know about the third option, running JS from a plugin. Interesting.)

             

            I'll be going with one of the first two.

             

            Notice that Text Layers really do have a first-class string parameter in them, expressions and all. Maybe PF_ParamtypeString, someday.

             

            /d