Opened 14 years ago
Closed 14 years ago
#9394 closed Patch - Feature (fixed)
Allow plugins to make system event calls
Reported by: | Owned by: | cpinkham | |
---|---|---|---|
Priority: | minor | Milestone: | 0.25 |
Component: | MythTV - General | Version: | Master Head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
Install extra header files so plugins can trigger system events
Attachments (3)
Change History (8)
Changed 14 years ago by
Attachment: | header.diff added |
---|
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Owner: | changed from beirdo to cpinkham |
---|---|
Status: | new → assigned |
Changed 14 years ago by
Attachment: | header2.diff added |
---|
comment:4 Changed 14 years ago by
Component: | MythTV - MythSystem → MythTV - General |
---|---|
Version: | Unspecified → Trunk Head |
The 'mythsystem' component is for the routines used to manage external executables.
comment:5 Changed 14 years ago by
Milestone: | unknown → 0.25 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Move main system event sender helper routine to MythCoreContext?.
This will allow any code with access to MythCoreContext? via the global gCoreContext to be able to send a MythSystemEvent?. This includes plugins and libmythbase.
Instead of this:
#include "mythsystemevent.h"
SendMythSystemEvent?("blah");
callers can now do this:
gCoreContext->SendSystemEvent?("blah");
Rather than replicating the code in RemoteSendMessage?() inside MythCoreContext?, RemoteSendMessage?() has been moved into MythCoreContext? as MythCoreContext::SendMessage?(). Ditto for RemoteSendEvent?() moving to MythCoreContext::SendEvent?(). Both of these were no longer true 'Remote' methods since they send the message or event locally when run from the mythbackend application.
Fixes #9394.
NOTE: This commit modifies the binary API verison, so make clean, etc..
Branch: master Changeset: 1df93f5e4c11194b60208d2da51122e29e176d31
Required by #9395