Squeak Class Documentation category index | class index  
 
NetworkTerminalMorph
  category: Morphic-Remote
  superclass: Morph
  subclasses: NullTerminalMorph

A morph used to communicate with a remote image. It sends all mouse/keyboard events to the remote side, and it displays canvas commands that are sent back.

instance methods
  as yet unclassified
  addScalingMenuItems:hand:
areasRemainingToFill:

  drawing
  drawOn:
forceToFront:
updateBackgroundForm

  event handling
  acceptDroppingMorph:event:
commResult:
handleKeyDown:
handleKeyUp:
handleKeystroke:
handleMouseDown:
handleMouseMove:
handleMouseUp:
handlerForMouseDown:
handlesMouseOver:
mouseEnter:
mouseLeave:
sendEvent:
sendEventAsIs:
wantsDroppedMorph:event:

  geometry
  extent:

  initialization
  connection:
initialize
openInStyle:
openScaled

  shutting down
  disconnect
requestBufferedConnection

  stepping and presenter
  step
stepTime

class methods
  instance creation
  connectTo:
connectTo:port:
openAndConnectTo:
openAndConnectTo:port:
socketConnectedTo:port:

instance methods
  as yet unclassified top  
 

addScalingMenuItems:hand:

for comaptibility when in scaled frame


 

areasRemainingToFill:

I assume that we are opaque


  drawing top  
 

drawOn:


 

forceToFront:

force the given region from the drawing form onto the background form


 

updateBackgroundForm

make sure that our background form matches what the server has most recently requested


  event handling top  
 

acceptDroppingMorph:event:

This message is sent when a morph is dropped onto a morph that has agreed to accept the dropped morph by responding 'true' to the wantsDroppedMorph:Event: message. This default implementation just adds the given morph to the receiver.


 

commResult:

ignore for now


 

handleKeyDown:

System level event handling.


 

handleKeyUp:

System level event handling.


 

handleKeystroke:

System level event handling.


 

handleMouseDown:

System level event handling.


 

handleMouseMove:

System level event handling.


 

handleMouseUp:

System level event handling.


 

handlerForMouseDown:

Return the (prospective) handler for a mouse down event. The handler is temporarily installed and can be used for morphs further down the hierarchy to negotiate whether the inner or the outer morph should finally handle the event


 

handlesMouseOver:

Do I want to receive mouseEnter: and mouseLeave: when the button is up and the hand is empty? The default response is false, except if you have added sensitivity to mouseEnter: or mouseLeave:, using the on:send:to: mechanism.


 

mouseEnter:

Handle a mouseEnter event, meaning the mouse just entered my bounds with no button pressed. The default response is to let my eventHandler, if any, handle it.


 

mouseLeave:

Handle a mouseLeave event, meaning the mouse just left my bounds with no button pressed. The default response is to let my eventHandler, if any, handle it.


 

sendEvent:


 

sendEventAsIs:


 

wantsDroppedMorph:event:

Return true if the receiver wishes to accept the given morph, which is being dropped by a hand in response to the given event. Note that for a successful drop operation both parties need to agree. The symmetric check is done automatically via aMorph wantsToBeDroppedInto: self.


  geometry top  
 

extent:


  initialization top  
 

connection:


 

initialize


 

openInStyle:


 

openScaled


  shutting down top  
 

disconnect


 

requestBufferedConnection


  stepping and presenter top  
 

step

Do some periodic activity. Use startStepping/stopStepping to start and stop getting sent this message. The time between steps is specified by this morph's answer to the stepTime message. The generic version dispatches control to the player, if any. The nasty circumlocation about owner's transformation is necessitated by the flexing problem that the player remains in the properties dictionary both of the flex and the real morph. In the current architecture, only the top renderer's pointer to the player should actually be honored for the purpose of firing.


 

stepTime

Answer the desired time between steps in milliseconds. This default implementation requests that the 'step' method be called once every second.


class methods
  instance creation top  
 

connectTo:


 

connectTo:port:


 

openAndConnectTo:


 

openAndConnectTo:port:


 

socketConnectedTo:port: