>At 1:27 AM +0100 20/5/1999, Scott Raney wrote:
>
>>>
>>> What would be impossible to predict by what?
>>
>>Without knowing the architecture of a particular application, someone
>>who came along and wanted to know what changes when button 1 is
>>pressed, they would be very hard pressed to figure this out (they'd
>>basically have to look at every single object to see if it was
>>watching button 1).
>
>Point taken, but if the watched object is now "independent" of other
>objects, we've less need to worry about how actions elsewhere affect it. On
>the other hand, currently, when we want to see why button x behaves (or
>misbehaves) as it does, it can be just as tough.
>
>But you've said enough to make me realise my original suggestion has some
>serious potential problems, particularly if applied in a general way to all
>properties of all objects. But there are some properties of some objects
>(the enabled state of buttons and the loc of various objects are the ones
>that come to mind) where something like this could be a great convenience,
>even if short on programming purity. But I guess it's back to the drawing
>board for now.
How about the setProp message being sent for user properties as well?
OK, performance could be a drawback, but with some effort, it can be
checked whenever a script is saved, not at runtime, couldn't it.
Regards
R�diger
--------------------------------------------------------------------
| 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 |
--------------------------------------------------------------------
