| Did you know ... | Search Documentation: |
| visual<-master |
stand-alone visual of this visual. This
definition is vague and its implementation is equally ill defined. The
idea is illustrated in the view <-> editor example:
If the programmer creates a view
object, s/he creates a specialised window with an editor displayed
inside it. The view delegates to its
editor object and the
programmer does not have to be aware that the view consists of multiple
objects. Class editor
however sometimes invokes associated messages (for example editor<->error_message.
We would like to retain the invisibility of the multiple objects by
binding @receiver
to the view rather than to the editor itself.
The visual<-master
method is a (bad, but we needed something) attempt to solve this
problem. It knows about some of these combinations and will return the
proper main object.
Defaults: Visual
objects that have not redefined this method return object<-self
Bugs: This method should not be there. As soon as a better
solution to this
composite object problem is found we will replace this.