Tag Plugin seems to be executed too often...

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 20/03/2010 at 12:07, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   11 
Platform:      Mac OSX  ; 
Language(s) :     C++  ;

---------
Rather by accident I found out that expression tags are basically executed in each mouseclick in numerous places, i.e.:

- Materials
- viewport
- objects
- tool switch

As most of these clicks could never affect my expressions, is there a way to reduce the number of calls to execute or any other strategy you would recommend?

Thanks!

Kabe

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 21/03/2010 at 02:11, xxxxxxxx wrote:

interesting question, btw **** if we "imitate" a parent constraint with getposition and get rotation, in a plugin tag, is that going to make all slower than adding "real" parent constraints?........

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 21/03/2010 at 23:55, xxxxxxxx wrote:

Interesting sidenote: ExPresso tags seem to suppress execution on viewport clicks, if this doesn't trigger any scene change. They do fire on clicks to the AM or the MM.

Kabe

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 22/03/2010 at 04:33, xxxxxxxx wrote:

It seems to happen only in dialogs that use tree lists. It looks almost like a bug. I will report this to the developers. The AM and the viewport triggers my test expression only if the click changes something.

cheers,
Matthias

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 22/03/2010 at 08:23, xxxxxxxx wrote:

In the concrete case it's an expression tag which should only react on scene changes.

Cheers

Klaus

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 23/03/2010 at 08:47, xxxxxxxx wrote:

I had the same problem, the expression was even executed when the mouse cursor hovered over the axis of an object in the viewport.
My approach was to do some checks in my Execute() function, checking e.g. if the scene time had changed, or if any of the participating objects were dirty.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 23/03/2010 at 09:31, xxxxxxxx wrote:

Could this be addressed by Message Handling? It seems strange to me that all the plugins would need to take their own measures to avoid superflous updates...

Kabe