This wiki is out of date, use the continuation of this wiki instead

Signals

From FenixWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 13:26, 1 May 2007 (edit)
Sandman (Talk | contribs)
m (category)
← Previous diff		 Current revision (20:31, 24 November 2008) (edit) (undo)
93.125.186.112 (Talk)
(→More info)
 
(7 intermediate revisions not shown.)
Line 1: Line 1:
-[[Category:global variables]]+[[Category:constantcategories]]
-[[Category:constant variables]]+
-The following signals can be sent from one process to another (these are [[predefined constants]] that can be passed as the "signal" parameter):+== Definition ==
-* [[s_kill]] - Order to kill the process. The process will not appear in the following [[frame]]s of the game any longer.+Signals are used to specify the signal to be sent to a [[process]] or all processes of a [[processType]], by passing one of them to the function [[signal]]() as the signal [[parameter]].
-* [[s_sleep]] - Order to make the process dormant. The process will remain paralyzed, without executing its code and without being displayed on screen (nor being detected by other processes), as if it had been killed. But the process will continue to exist in the computer's memory.+ 
-* [[s_freeze]] - Order to freeze the process. The process will remain motionless without running its code. But it will continue to be displayed on screen and it will be possible to detect it (in the collisions) by the rest of the processes. The process will continue to exist in the computers memory even if its code is not executed.+== List ==
-* [[s_wakeup]] - Order to wake up the process. It returns a slept or frozen process to its normal state. The process will be executed and displayed again from the moment that it recieves theis signal normally. A process that has been killed cannot be returned to its normal state by this method (or at all).+{|
 +| ''Constant'' || - ''Value'' || - ''Description''
 +|-
 +| S_KILL || - 0 || - Kill the process.
 +|-
 +| S_WAKEUP || - 1 || - Wakeup the process.
 +|-
 +| S_SLEEP || - 2 || - Put the process to sleep.
 +|-
 +| S_FREEZE || - 3 || - Freeze the process.
 +|-
 +| S_KILL_TREE || - 100 || - Kill the process and all its connected descendants.
 +|-
 +| S_WAKEUP_TREE || - 101 || - Wakeup the process and all its connected descendants.
 +|-
 +| S_SLEEP_TREE || - 102 || - Put the process and all its connected descendants to sleep.
 +|-
 +| S_FREEZE_TREE || - 103 || - Freeze the process and all its connected descendants.
 +|}
 +A descendant is connected when all its ascendants up until the process are still alive.
 + 
 +== More info ==
 + 
 +* S_KILL - Order to kill the process. The process will not appear in the following [[frame]]s of the game any longer.
 +* S_WAKEUP - Order to wake up the process. It returns a slept or frozen process to its normal state. The process will be executed and displayed again from the moment that it recieves theis signal normally. A process that has been killed cannot be returned to its normal state by this method (or at all).
 +The process will restore itself from the next Frame; statement it encounters after the signal was issued (use a Frame(0); statement to resume the code from a specific point)
 +* S_SLEEP - Order to make the process dormant. The process will remain paralyzed, without executing its code and without being displayed on screen (nor being detected by other processes), as if it had been killed. But the process will continue to exist in the computer's memory.
 +* S_FREEZE - Order to freeze the process. The process will remain motionless without running its code. But it will continue to be displayed on screen and it will be possible to detect it (in the collisions) by the rest of the processes. The process will continue to exist in the computers memory even if its code is not executed.
In addition to these there are the following signals that have the same effect, but affect a range of processes, not just a single process: In addition to these there are the following signals that have the same effect, but affect a range of processes, not just a single process:
-* [[s_kill_tree]]+* S_KILL_TREE
-* [[s_sleep_tree]]+* S_WAKEUP_TREE
-* [[s_freeze_tree]]+* S_SLEEP_TREE
-* [[s_wakeup_tree]]+* S_FREEZE_TREE
-These will have the effect of their non-tree counterparts, but will affect the process indicated by the "processID" or "processName" parameter and all of the processes created by those processes, either directly, or indirectly. So if an [[s_kill_tree]] signal is sent to a process, that process will die, all of the processes that it created will die, and all of the processes that they created will die, and so on. The exception to this is where there is an [[orphan process]], that is a process to whose [[father]] is already dead.+These will have the effect of their non-tree counterparts, but will affect the process indicated by the [[processID]]|[[processTypeID]] parameter and all of the processes created by those processes, either directly, or indirectly. So if an S_KILL_TREE signal is sent to a process, that process will die, all of the processes that it created will die, and all of the processes that they created will die, and so on. The exception to this is where there is an [[orphan process]], that is a process to whose [[father]] is already dead. This exception cannot occur in later (''which one?'') [[Fenix]] versions or [[Bennu]], because when a process gets killed, its father will inherit its children, so orphaned processes can't exist.

Current revision


[edit] Definition

Signals are used to specify the signal to be sent to a process or all processes of a processType, by passing one of them to the function signal() as the signal parameter.

[edit] List

Constant - Value - Description
S_KILL - 0 - Kill the process.
S_WAKEUP - 1 - Wakeup the process.
S_SLEEP - 2 - Put the process to sleep.
S_FREEZE - 3 - Freeze the process.
S_KILL_TREE - 100 - Kill the process and all its connected descendants.
S_WAKEUP_TREE - 101 - Wakeup the process and all its connected descendants.
S_SLEEP_TREE - 102 - Put the process and all its connected descendants to sleep.
S_FREEZE_TREE - 103 - Freeze the process and all its connected descendants.

A descendant is connected when all its ascendants up until the process are still alive.

[edit] More info

  • S_KILL - Order to kill the process. The process will not appear in the following frames of the game any longer.
  • S_WAKEUP - Order to wake up the process. It returns a slept or frozen process to its normal state. The process will be executed and displayed again from the moment that it recieves theis signal normally. A process that has been killed cannot be returned to its normal state by this method (or at all).

The process will restore itself from the next Frame; statement it encounters after the signal was issued (use a Frame(0); statement to resume the code from a specific point)

  • S_SLEEP - Order to make the process dormant. The process will remain paralyzed, without executing its code and without being displayed on screen (nor being detected by other processes), as if it had been killed. But the process will continue to exist in the computer's memory.
  • S_FREEZE - Order to freeze the process. The process will remain motionless without running its code. But it will continue to be displayed on screen and it will be possible to detect it (in the collisions) by the rest of the processes. The process will continue to exist in the computers memory even if its code is not executed.

In addition to these there are the following signals that have the same effect, but affect a range of processes, not just a single process:

  • S_KILL_TREE
  • S_WAKEUP_TREE
  • S_SLEEP_TREE
  • S_FREEZE_TREE

These will have the effect of their non-tree counterparts, but will affect the process indicated by the processID|processTypeID parameter and all of the processes created by those processes, either directly, or indirectly. So if an S_KILL_TREE signal is sent to a process, that process will die, all of the processes that it created will die, and all of the processes that they created will die, and so on. The exception to this is where there is an orphan process, that is a process to whose father is already dead. This exception cannot occur in later (which one?) Fenix versions or Bennu, because when a process gets killed, its father will inherit its children, so orphaned processes can't exist.

Retrieved from "http://www.fenixdocs.com/index.php/Signals"
Personal tools