Ticket #444 (new defect)
oeventsd doesn't care about SMS.IncomingMessage signal
| Reported by: | dos | Owned by: | jluebbe |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | framework/oeventsd | Version: | |
| Keywords: | HasPatch | Cc: |
Description
With SimBuffersSms?(False) oeventsd ignores incoming message - IncomingMessage? trigger is not called. This is due to this code, which looks only at SIM.IncomingStoredMessage? signal in fso_triggers.py:
#============================================================================# class IncomingMessageTrigger?(DBusTrigger): #============================================================================#
""" A custom dbus trigger for org.freesmartphone.GSM.SIM.IncomingStoredMessage? """
function_name = 'IncomingMessage?'
def init(self):
bus = dbus.SystemBus?() super(IncomingMessageTrigger?, self).init(
bus, 'org.freesmartphone.ogsmd', '/org/freesmartphone/GSM/Device', 'org.freesmartphone.GSM.SIM', 'IncomingStoredMessage?'
)
def on_signal(self, index):
logger.info("Receive IncomingMessage? on index = %s" % index) self._trigger(index=index)
def repr(self):
return "IncomingMessage?"
Locally I have it changed to opimd signals, but I don't think we can set it as default until ms5.5 is released.
Attachments
Change History
comment:1 Changed 3 years ago by dos
Milestone 5.5 is released, we can start thinking about PIM integration.
I've attached patch for making IncomingMessage? trigger to use opimd interface.
comment:3 Changed 3 years ago by stefan
Daniel, what's your opinion here?
I don't know where we like to draw the line for PIM. For me SMS/E-Mail/IM does not belong to it, but I know other people may disagree.
comment:4 Changed 2 years ago by sim
decoration Changed 1 year ago by admin
bathtub Changed 1 year ago by admin
solar system Changed 1 year ago by admin
stair parts Changed 1 year ago by admin
solar supply Changed 1 year ago by admin

