1.182.2 Get methods

visual <-contained_in: -> visual

Returns the parent visualiser. Defined at each of the various subclasses of visualiser to deal with the different implementations. All visualiser classes define this method. The object @display_manager is the root of the hierarchy.

See also visual<-contains. Using the manpce/0 window, the menu Tools/Visual hierachy provides a tool for inspecting the actual hierarchy.

See also

- frame<-contained_in
- window<-contained_in
- visual<-contains

visual <-container: class|code -> condition=visual

Find the innermost graphical in the consists-of hierarchy defined by class visual and its sub-classes that satisfies the given condition. Arguments:

@arg1		Visual object considered

Providing a class argument is a shorthand for

message(@arg1, instance_of, <class>).

See also visual<-contains, visual<-contained_in, graphical<-window, graphical<-frame and graphical<-display.

visual <-contains: -> chain

Returns a chain with the visualisers of the next level of the contains hierarchy. Each of the subclasses that defines a compound visualiser defines this method to deal with it's particular implementation.

See also

- frame<-contains
- visual->destroy
- device<-contains
- visual<-contained_in

visual <-frame: -> frame

Frame I'm part of (if present). This method uses visual<-contained_in to walk up the consists-of hierarchy of graphical objects until it finds and instance of class frame. Fails silently if no frame can be found, which is the case if the receiver is not displayed, is a display object or @display_manager.

See also visual<-container, graphical<-window and graphical<-device

visual <-master: -> visual

Returns the 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.

visual <-report_to: -> visual

Object capable of handling a visual->report. By default this is the same as visual<-contained_in.

See also

dialog<-report_to