I tried using the CDK. It works OK when debugging the application, but not
for the *.EXE (..I know...it works only with the outline....).
Maybe some of the XSal(xxx) products?
Thanks.
Juan Ignacio Saitua.
--
Regards,
Frank Boettcher
Ice Tea Group, LLC
http://www.iceteagroup.com
"Juan Ignacio Saitua" <jisa...@cge.cl> schrieb im Newsbeitrag
news:eJFgkQz...@talkto.centurasoft.com...
But, what about the SalCompileAndEvaluate function?
For example look this program, that sets some attribute of an object at
run-time:
_____________________________________
Set aPerson = new cPersona
Set anyString = df1
set attName = df2
Set strExpression = 'Set aPerson.' || attName || '= anyString'
Set nType = SalCompileAndEvaluate ( strExpression, nError, nErrorPos,
nReturn, strReturn, dtReturn, hWndReturn, TRUE, SalContextCurrent() )
____________________________________
With this sample whe're setting at run-time any string attribute of a
cPersona object.
I think, that in some place there are the attribute-labels of cPerson: name,
direction, because the program 'knows' how to evaluate strExpression. If so,
would be possible to retrieve that info for the object?
Any comment about this?
Thank you!
Juan Ignacio Saitua.
from a discussion with someone at CNTR I recall that this interface
is not exposed through the cdk. SalCompileAndEvaluate use
a name and scope to determine the corresponding HITEM (and the value).
AFAIK these internas have never been (and will never be?) exposed through
the CDK.
Of course this is just my guess.
Sorry,
Frank
"Juan Ignacio Saitua" <jisa...@cge.cl> schrieb im Newsbeitrag
news:gBKuuJ8...@talkto.centurasoft.com...
^^^^^^^^^^^^^
Any comment about this from the Oficial Centura Team? IMHO it would be an
interesting feature for the developers.....
Regards, and thank you Frank for the info.
Juan Ignacio Saitua.