so far so good. :-)

take a look at the "supervisor" sample project.

it shows the code to hide/shows params.

as for hiding topics, you need to hide both the topic param, and all the params in it.

if you hide only the topic, the params might still show up under certain circumstances. (such as the user pressing 'U' when a hidden param has keyframes)

you don't need to hide/show the "topic end" param. just leave that one be.

taken from the supervisor sample:

                    ERR(suites.PFInterfaceSuite1()->AEGP_GetNewEffectForEffect(globP->my_id, in_data->effect_ref, &meH));

                    ERR(suites.StreamSuite2()->AEGP_GetNewEffectStreamByIndex(globP->my_id, meH, SUPER_FLAVOR,           &flavor_streamH));

  // Toggle visibility of parameters

  ERR(suites.DynamicStreamSuite2()->AEGP_SetDynamicStreamFlag(flavor_streamH, AEGP_DynStreamFlag_HIDDEN, FALSE, hide_themB));

the code seems correct.

i use the same method with no problem.

after what line does the crash occur?

during what call are you executing these lines?

hmmm....

all seems ok...

a couple of things:

1. use a NULL instead of globP->my_id

2. who owns &meH? how was it created?

3. do previous calls to suites in the same scope work? (i.e. is it this specific line, or is it simply the first to be called)

well, if i'm not mistaking, my_id is not a parameter passed by AE to you.

the global data is a structure you create according to your plug-in's needs.

so most probably, you have it just because it was there in a sample project you're based on. (my apologies if otherwise...)

if memory serves, my_id is usually populated by the call to registerWithAegp() (or something similar, usually in the global_setup() function).

historically, the AEGP suites were used exclusively by AEGPs and not effects.

so to use the suites, an effect had to register as an aegp, and get it's id.

some suites do require the use of an ID, but most suffice with a NULL.

so why the crash?

if my_id is just a variable in the global data structure, and it was never assigned a value via the registry operation, then you're telling AE to go look for you at some random - non existing place.

crash, burn, screams, horror.

all that is true only if you indeed did not register with AEGP and gotten your id properly...

:-)

AEGP_SetStreamName()

first of all, i was not aware of the method you suggested, so thanks for

the info!

as for the differences...

the SetStreamName thingie can be called at any time, including to and by

other plug-ins.

you can change the name of any stream you can get your hands on, and not

only for self.

i have no idea if the same applies to your method. (though intuitively i'd

think it doesn't)

there also has to be some difference in performance times.

i would imagine that difference being neglegible, though in large number it

might be noticeable. (in my plug-in i change hundreds of param names at a

time).