Updating a custom effect and caching
Hello. I'm Andy, a new Captivate user. It's been an interesting week discovering many of the delights, and a few too many of the frustrations, of Captivate 9. Most of the issues I have encountered I have managed to find a resolution for, one way or another but often using these forums, so thank you to all contributors.
There is one issue that I have been unable to resolve, though trying to resolve it has led me to a greater understanding of Captivate, so silver linings. It is this...
I have created a custom effect by editing an existing effect, giving it a new name and loading it via the browse effect button on the effects panel. It works just fine on the timeline and, following directions from the omniscient Lilybiri, I get it to work fine in Advanced Actions too. All good. Now I want to tweak one of the parameters of that custom effect, in particular I want to extend the range of possible values of that parameter, so I edit the xml. But back in my project my edits seem to be ignored and the effect continues to allow me only the original range of possible values.
- Suspecting a caching issue I clear the cache but this does not make any difference.
- I delete the original xml file and load in the amended one (with the same name) from the effects panel but my amended one will not load - I get an error (from memory "Invalid Effect File"). The effect file is not invalid (see points 3 and 4) so I suspect it is complaining that I am trying to load an effect with the same name as one I have already used in my project.
- I load the amended custom effect for the first time in a new project and this works fine.
- I give my amended custom effect xml file a new name and back in my original project I load that newly named effect instead. This works fine and the new parameter range is finally active but now I have two versions of my effect: the original one I no longer want, and to which so many of my objects are linked, and the new one that I do want, but to which none of my objects is linked.
- I'm as lazy as the next person so I don't want to change all of the uses of my custom effect to the newly named one. This will work but why should I have to do that? Also I want my projects to be clean - they should contain only the elements I want and nothing else (a tidy project is a tidy mind etc. etc.). I am likely to dream up further change to custom effects at some later date and it really ought to be simple to reload these effects.
My conclusion is this: that loading a custom effect into a project is a "no turning back" event. Once loaded it is forever encapsulated in to the project and no amount of janitor work will allow it to be cleaned out or upgraded. I suspect also that this is the same for out-of-the box effects.
I'd be grateful to anyone who can confirm this, and so stop me trying ever more deparate things to make my update just work without re-engineering my project.
I'd be even more grateful to anyone who can describe a way to edit a custom effect and have my project objects use that edited effect without me having to reload the effect under a new name and relink everything to that new effect.
Thanks,
Andy.
