mod_program

Circuit components of modular programs are special. They're added to the unremovable components of the shell when the prog is installed and deleted if uninstalled. This means they don't work like normal unremovable comps that live and die along with their shell.

Vars
associated_program	The program that installed us into the shell/usb_port comp. Needed to avoid having too many signals for every program. This is also the program we need to install on the modular computer if the circuit is admin-loaded. Just make sure each of these components is associated to one and only type of program, no subtypes of anything.
kill	kills the program.
running	binary for whether the program is running or not
start	Starts the program if possible, placing it in the background if another's active.
Procs
should_receive_input	For most programs, triggers only work if they're open (either active or idle).

Var Details

var
associated_program
– /datum/computer_file/program

The program that installed us into the shell/usb_port comp. Needed to avoid having too many signals for every program. This is also the program we need to install on the modular computer if the circuit is admin-loaded. Just make sure each of these components is associated to one and only type of program, no subtypes of anything.

var
kill
– /datum/port/input

kills the program.

var
running
– /datum/port/output

binary for whether the program is running or not

var
start
– /datum/port/input

Starts the program if possible, placing it in the background if another's active.

Proc Details

↑
should_receive_input
(/datum/port/input/port)

For most programs, triggers only work if they're open (either active or idle).

mod_program /obj/item/circuit_component/mod_program

Vars

Procs

Var Details

var associated_program – /datum/computer_file/program

var kill – /datum/port/input

var running – /datum/port/output

var start – /datum/port/input