Re: Graphics/control panel problems

[manor]

> I wondered about this "probing the bugs with a mouse clicks" too. As I
> noticed by reading the code, there are no parameters behind X: and Y:.
>
> [worldRaster setButton: ButtonRight Client: heatbugDisplay Message:
> M(makeProbeAtX:Y:)];

This is not the actual message call. M() is a macro for @selector() which
takes the name of a message and returns a selector for it, the arguments
are added when an actual button-click occurs (in Raster.m):

==========================================================================

  -handleButton: (int) n X: (int) x Y: (int) y {
    id c = 0;
    SEL sel = 0;
    switch(n) {
      case 1: c = button1Client; sel = button1Sel; break;
      case 2: c = button2Client; sel = button2Sel; break;
      case 3: c = button3Client; sel = button3Sel; break;
      default: raiseEvent(SourceMessage, "Button %d out of range.\n");
    }

    if (c && sel)
------>   [c perform: sel with: (void *) x with: (void *) y]; <------
    return self;
  }

==========================================================================

That's the theory, anyway...

Manor.

                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.
                  ==================================