IdScriptableObject newIdFunction

[darrel karisch]

what is the rationale for the private declaration of
IdScriptableObject::newIdFunction?

I have created IdScriptableObject subclasses and want to extend
IdFunctionObject so that I can perform other tasks within its methods.

the private declaration prevents this.

[Hannes Wallnoefer]

Why not write your own method that creates your extended
IdFunctionObject? It's only three lines and doesn't touch any private
fields or methods.

hannes

[darrel karisch]

that is my point. I want to have a custom newIdFunction that is
invoked from IdScriptableObject when required. however, the private
declaration prevents my overridden method from being invoked. it must
be protected (or public) to achieve this behavior.

[darrel karisch]

that is my point. I want to have a custom newIdFunction that is

invoked within IdScriptableObject methods as required. however, the

private declaration prevents my overridden method from being invoked.
it must be protected (or public) to achieve this behavior.

thanks for your prompt responses.

[darrel karisch]

can one of you committers take a look at this for R1.7.2?

as I responded to Hannes in an email, I could override
initPrototypeMethod() and addIdFunctionProperty() and return my own
subclass of IdFunctionObject in the implementations. however, I then
have to support that much more code and remain vigilant to future
IdScriptableObject changes in those methods. the further away I stay
from those details the better off I am.

I think a better solution is merely to open up the design. I suspect
you would agree.

thanks for your consideration.

darrel