Scott Raney wrote:
> One way to do this would be to have a function that does this, similar
> to the way the selectedField() or the foundField() work. How about:
> put "button 1" into X
> put "whatever" into objectReference(X)
>
> It might also be possible to do it by adding a new chunk type "object"
> that implies a dereference:
> put "button 1" into X
> put "whatever" into object X
>
> But the latter could get hairy to implement:
> put "whatever" into object X of stack "somestack"
Is "object" not a synonym for control et. al. for OMO compatibility?!?
Even if is was not, the term object should then be reserved for a better
use than object dereference.
I like the function better, abbreviated by "objRef".
Regards
R�diger (when will there be a voting mechanism)
--------------------------------------------------------------------
| Ruediger zu Dohna GINIT GmbH 0721-96681-63 [EMAIL PROTECTED] |
| PGP-Fingerprint: F1 BF 9D 95 57 26 48 42 FE F8 E8 02 41 1A EE 3E |
--------------------------------------------------------------------
