On 7/25/06, Mathieu Bouchard matju@artengine.ca wrote:
I like the concept of a non-GUI object being two-way-connected to a GUI object, or else a GUI object containing a non-GUI object acting as a user-oriented wrapper for that non-GUI object. The first of those two options is more flexible because the non-GUI object is not hardcoded, so the GUI part can be used with different non-GUI objects, provided that the non-GUI objects follow the same conventions.
I've wondered about this first way. Would you need a [change] object or something, though, to keep from starting a loop? Or a [set $1( message? -Chuckk