jp9000/obs-studio
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

(API Change) Use 'get' convention in libobs (base)

Browse Source 
Instead of having functions like obs_signal_handler() that can fail to
properly specify their actual intent in the name (does it signal a
handler, or does it return a signal handler?), always prefix functions
that are meant to get information with 'get' to make its functionality
more explicit.

Previous names:             New names:
-----------------------------------------------------------
obs_audio                   obs_get_audio
obs_video                   obs_get_video
obs_signalhandler           obs_get_signal_handler
obs_prochandler             obs_get_proc_handler
obs_source_signalhandler    obs_source_get_signal_handler
obs_source_prochandler      obs_source_get_proc_handler
obs_output_signalhandler    obs_output_get_signal_handler
obs_output_prochandler      obs_output_get_proc_handler
obs_service_signalhandler   obs_service_get_signal_handler
obs_service_prochandler     obs_service_get_proc_handler
This commit is contained in:
jp9000
2014-08-04 09:09:02 -07:00
parent 73baaa59e9
commit a3682fc8fb
12 changed files with 50 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
libobs/obs-service.c
View File

@@ -167,12 +167,12 @@ obs_data_t obs_service_get_settings(obs_service_t service)
return service->context.settings;
}
signal_handler_t obs_service_signalhandler(obs_service_t service)
signal_handler_t obs_service_get_signal_handler(obs_service_t service)
{
return service ? service->context.signals : NULL;
}
proc_handler_t obs_service_prochandler(obs_service_t service)
proc_handler_t obs_service_get_proc_handler(obs_service_t service)
{
return service ? service->context.procs : NULL;
}