In bigger systems references seem to be very slow, particularly in control panels where you’re setting the size of a child container to it’s parent parameters and with custom parameters.
It’d be great if there were a way these were actually exports in the back end if there are no extra bits and bobs (such as for example: me.parent().par.w*2) or perhaps if there were an update to exporting to make this faster. Right now I’ve got parameter executes doing half the work which seems a bit backwards.
Yes, we’re working on a few schemes to make expressions in parameters much faster, as we are seeing the same artifacts, both in simple expressions as you say, and in operators with a bunch of expressions that get over-cooked. We don’t want anyone to shy away from expressions in parameters, so this is a priority for us.
that’s good to hear Greg. References are such a userfriendly joy to work with in parameters in comparison to exports, I’d rather have References everywhere in my projects - but as richard said, on heavy large projects I’m replacing them with exports to win FPS.
+1 had to do the same for a bunch of high frame rate projects recently. Replaced all Python with tscript, exports, and scripts writing constant values to parameters.