mirror of
https://github.com/Bubberstation/Bubberstation.git
synced 2026-07-12 00:27:31 +01:00
Grep for space indentation (#54850)
#54604 atomizing Since a lot of the space indents are in lists ill atomize those later
This commit is contained in:
TiviPlus
@@ -89,15 +89,15 @@
|
||||
return TRUE
|
||||
|
||||
/**
|
||||
*Check if the user can run program. Only humans can operate computer. Automatically called in run_program()
|
||||
*ID must be inserted into a card slot to be read. If the program is not currently installed (as is the case when
|
||||
*NT Software Hub is checking available software), a list can be given to be used instead.
|
||||
*Arguments:
|
||||
*user is a ref of the mob using the device.
|
||||
*loud is a bool deciding if this proc should use to_chats
|
||||
*access_to_check is an access level that will be checked against the ID
|
||||
*transfer, if TRUE and access_to_check is null, will tell this proc to use the program's transfer_access in place of access_to_check
|
||||
*access can contain a list of access numbers to check against. If access is not empty, it will be used istead of checking any inserted ID.
|
||||
*Check if the user can run program. Only humans can operate computer. Automatically called in run_program()
|
||||
*ID must be inserted into a card slot to be read. If the program is not currently installed (as is the case when
|
||||
*NT Software Hub is checking available software), a list can be given to be used instead.
|
||||
*Arguments:
|
||||
*user is a ref of the mob using the device.
|
||||
*loud is a bool deciding if this proc should use to_chats
|
||||
*access_to_check is an access level that will be checked against the ID
|
||||
*transfer, if TRUE and access_to_check is null, will tell this proc to use the program's transfer_access in place of access_to_check
|
||||
*access can contain a list of access numbers to check against. If access is not empty, it will be used istead of checking any inserted ID.
|
||||
*/
|
||||
/datum/computer_file/program/proc/can_run(mob/user, loud = FALSE, access_to_check, transfer = FALSE, list/access)
|
||||
// Defaults to required_access
|
||||
@@ -159,15 +159,15 @@
|
||||
return FALSE
|
||||
|
||||
/**
|
||||
*
|
||||
*Called by the device when it is emagged.
|
||||
*
|
||||
*Emagging the device allows certain programs to unlock new functions. However, the program will
|
||||
*need to be downloaded first, and then handle the unlock on their own in their run_emag() proc.
|
||||
*The device will allow an emag to be run multiple times, so the user can re-emag to run the
|
||||
*override again, should they download something new. The run_emag() proc should return TRUE if
|
||||
*the emagging affected anything, and FALSE if no change was made (already emagged, or has no
|
||||
*emag functions).
|
||||
*
|
||||
*Called by the device when it is emagged.
|
||||
*
|
||||
*Emagging the device allows certain programs to unlock new functions. However, the program will
|
||||
*need to be downloaded first, and then handle the unlock on their own in their run_emag() proc.
|
||||
*The device will allow an emag to be run multiple times, so the user can re-emag to run the
|
||||
*override again, should they download something new. The run_emag() proc should return TRUE if
|
||||
*the emagging affected anything, and FALSE if no change was made (already emagged, or has no
|
||||
*emag functions).
|
||||
**/
|
||||
/datum/computer_file/program/proc/run_emag()
|
||||
return FALSE
|
||||
|
||||
@@ -74,13 +74,13 @@
|
||||
scan()
|
||||
|
||||
/**
|
||||
*Updates tracking information of the selected target.
|
||||
*
|
||||
*The track() proc updates the entire set of information about the location
|
||||
*of the target, including whether the Ntos window should use a pinpointer
|
||||
*crosshair over the up/down arrows, or none in favor of a rotating arrow
|
||||
*for far away targets. This information is returned in the form of a list.
|
||||
*
|
||||
*Updates tracking information of the selected target.
|
||||
*
|
||||
*The track() proc updates the entire set of information about the location
|
||||
*of the target, including whether the Ntos window should use a pinpointer
|
||||
*crosshair over the up/down arrows, or none in favor of a rotating arrow
|
||||
*for far away targets. This information is returned in the form of a list.
|
||||
*
|
||||
*/
|
||||
/datum/computer_file/program/radar/proc/track()
|
||||
var/atom/movable/signal = find_atom()
|
||||
@@ -116,13 +116,13 @@
|
||||
return trackinfo
|
||||
|
||||
/**
|
||||
*
|
||||
*Checks the trackability of the selected target.
|
||||
*
|
||||
*If the target is on the computer's Z level, or both are on station Z
|
||||
*levels, and the target isn't untrackable, return TRUE.
|
||||
*Arguments:
|
||||
**arg1 is the atom being evaluated.
|
||||
*
|
||||
*Checks the trackability of the selected target.
|
||||
*
|
||||
*If the target is on the computer's Z level, or both are on station Z
|
||||
*levels, and the target isn't untrackable, return TRUE.
|
||||
*Arguments:
|
||||
**arg1 is the atom being evaluated.
|
||||
*/
|
||||
/datum/computer_file/program/radar/proc/trackable(atom/movable/signal)
|
||||
if(!signal || !computer)
|
||||
@@ -134,30 +134,30 @@
|
||||
return (there.z == here.z) || (is_station_level(here.z) && is_station_level(there.z))
|
||||
|
||||
/**
|
||||
*
|
||||
*Runs a scan of all the trackable atoms.
|
||||
*
|
||||
*Checks each entry in the GLOB of the specific trackable atoms against
|
||||
*the track() proc, and fill the objects list with lists containing the
|
||||
*atoms' names and REFs. The objects list is handed to the tgui screen
|
||||
*for displaying to, and being selected by, the user. A two second
|
||||
*sleep is used to delay the scan, both for thematical reasons as well
|
||||
*as to limit the load players may place on the server using these
|
||||
*somewhat costly loops.
|
||||
*
|
||||
*Runs a scan of all the trackable atoms.
|
||||
*
|
||||
*Checks each entry in the GLOB of the specific trackable atoms against
|
||||
*the track() proc, and fill the objects list with lists containing the
|
||||
*atoms' names and REFs. The objects list is handed to the tgui screen
|
||||
*for displaying to, and being selected by, the user. A two second
|
||||
*sleep is used to delay the scan, both for thematical reasons as well
|
||||
*as to limit the load players may place on the server using these
|
||||
*somewhat costly loops.
|
||||
*/
|
||||
/datum/computer_file/program/radar/proc/scan()
|
||||
return
|
||||
|
||||
/**
|
||||
*
|
||||
*Finds the atom in the appropriate list that the `selected` var indicates
|
||||
*
|
||||
*The `selected` var holds a REF, which is a string. A mob REF may be
|
||||
*something like "mob_209". In order to find the actual atom, we need
|
||||
*to search the appropriate list for the REF string. This is dependant
|
||||
*on the program (Lifeline uses GLOB.human_list, while Fission360 uses
|
||||
*GLOB.poi_list), but the result will be the same; evaluate the string and
|
||||
*return an atom reference.
|
||||
*
|
||||
*Finds the atom in the appropriate list that the `selected` var indicates
|
||||
*
|
||||
*The `selected` var holds a REF, which is a string. A mob REF may be
|
||||
*something like "mob_209". In order to find the actual atom, we need
|
||||
*to search the appropriate list for the REF string. This is dependant
|
||||
*on the program (Lifeline uses GLOB.human_list, while Fission360 uses
|
||||
*GLOB.poi_list), but the result will be the same; evaluate the string and
|
||||
*return an atom reference.
|
||||
*/
|
||||
/datum/computer_file/program/radar/proc/find_atom()
|
||||
return
|
||||
|
||||
@@ -135,11 +135,11 @@
|
||||
borgo.toggle_headlamp(FALSE, TRUE)
|
||||
|
||||
/**
|
||||
* Forces a full update of the UI, if currently open.
|
||||
*
|
||||
* Forces an update that includes refreshing ui_static_data. Called by
|
||||
* law changes and borg log additions.
|
||||
*/
|
||||
* Forces a full update of the UI, if currently open.
|
||||
*
|
||||
* Forces an update that includes refreshing ui_static_data. Called by
|
||||
* law changes and borg log additions.
|
||||
*/
|
||||
/datum/computer_file/program/robotact/proc/force_full_update()
|
||||
if(tablet)
|
||||
var/datum/tgui/active_ui = SStgui.get_open_ui(tablet.borgo, src)
|
||||
|
||||
@@ -60,11 +60,11 @@
|
||||
. = max(., S.get_status())
|
||||
|
||||
/**
|
||||
* Sets up the signal listener for Supermatter delaminations.
|
||||
*
|
||||
* Unregisters any old listners for SM delams, and then registers one for the SM refered
|
||||
* to in the `active` variable. This proc is also used with no active SM to simply clear
|
||||
* the signal and exit.
|
||||
* Sets up the signal listener for Supermatter delaminations.
|
||||
*
|
||||
* Unregisters any old listners for SM delams, and then registers one for the SM refered
|
||||
* to in the `active` variable. This proc is also used with no active SM to simply clear
|
||||
* the signal and exit.
|
||||
*/
|
||||
/datum/computer_file/program/supermatter_monitor/proc/set_signals()
|
||||
if(active)
|
||||
@@ -72,9 +72,9 @@
|
||||
RegisterSignal(active, COMSIG_SUPERMATTER_DELAM_START_ALARM, .proc/send_start_alert, override = TRUE)
|
||||
|
||||
/**
|
||||
* Removes the signal listener for Supermatter delaminations from the selected supermatter.
|
||||
*
|
||||
* Pretty much does what it says.
|
||||
* Removes the signal listener for Supermatter delaminations from the selected supermatter.
|
||||
*
|
||||
* Pretty much does what it says.
|
||||
*/
|
||||
/datum/computer_file/program/supermatter_monitor/proc/clear_signals()
|
||||
if(active)
|
||||
@@ -82,12 +82,12 @@
|
||||
UnregisterSignal(active, COMSIG_SUPERMATTER_DELAM_START_ALARM)
|
||||
|
||||
/**
|
||||
* Sends an SM delam alert to the computer.
|
||||
*
|
||||
* Triggered by a signal from the selected supermatter, this proc sends a notification
|
||||
* to the computer if the program is either closed or minimized. We do not send these
|
||||
* notifications to the comptuer if we're the active program, because engineers fixing
|
||||
* the supermatter probably don't need constant beeping to distract them.
|
||||
* Sends an SM delam alert to the computer.
|
||||
*
|
||||
* Triggered by a signal from the selected supermatter, this proc sends a notification
|
||||
* to the computer if the program is either closed or minimized. We do not send these
|
||||
* notifications to the comptuer if we're the active program, because engineers fixing
|
||||
* the supermatter probably don't need constant beeping to distract them.
|
||||
*/
|
||||
/datum/computer_file/program/supermatter_monitor/proc/send_alert()
|
||||
if(!computer.get_ntnet_status())
|
||||
@@ -97,13 +97,13 @@
|
||||
alert_pending = TRUE
|
||||
|
||||
/**
|
||||
* Sends an SM delam start alert to the computer.
|
||||
*
|
||||
* Triggered by a signal from the selected supermatter at the start of a delamination,
|
||||
* this proc sends a notification to the computer if this program is the active one.
|
||||
* We do this so that people carrying a tablet with NT CIMS open but with the NTOS window
|
||||
* closed will still get one audio alert. This is not sent to computers with the program
|
||||
* minimized or closed to avoid double-notifications.
|
||||
* Sends an SM delam start alert to the computer.
|
||||
*
|
||||
* Triggered by a signal from the selected supermatter at the start of a delamination,
|
||||
* this proc sends a notification to the computer if this program is the active one.
|
||||
* We do this so that people carrying a tablet with NT CIMS open but with the NTOS window
|
||||
* closed will still get one audio alert. This is not sent to computers with the program
|
||||
* minimized or closed to avoid double-notifications.
|
||||
*/
|
||||
/datum/computer_file/program/supermatter_monitor/proc/send_start_alert()
|
||||
if(!computer.get_ntnet_status())
|
||||
|
||||
Reference in New Issue
Block a user