Currently the L0tx object initialises from a .msg file, which is a transmission message along with the .sbd file as an attachment. Ideally, we should also be able to initialise a L0tx object from just the attachment (i.e. initialise with a .msg file OR a .sbd file). This way, our back-up of transmissions could be reduced to just the attachments.
In order to do this, the L0tx object needs to be redesigned with flexible initialisation. Right now, L0tx inherits from the EmailMessage and SbdMessage objects, where an EmailMessage represents the contents of the transmission message and SbdMessage represents the contents of the .sbd attachment; like so:
So we need to build flexibility so that the L0tx object can initialise from the .sbd file, creating the SbdMessage object and a practically empty EmailMessage object.
The only thing to note is that by doing this, we lose the logger GPS information which is only included in the transmission message and NOT the attachment.
Currently the
L0txobject initialises from a.msgfile, which is a transmission message along with the.sbdfile as an attachment. Ideally, we should also be able to initialise aL0txobject from just the attachment (i.e. initialise with a.msgfile OR a.sbdfile). This way, our back-up of transmissions could be reduced to just the attachments.In order to do this, the
L0txobject needs to be redesigned with flexible initialisation. Right now,L0txinherits from theEmailMessageandSbdMessageobjects, where anEmailMessagerepresents the contents of the transmission message andSbdMessagerepresents the contents of the.sbdattachment; like so:So we need to build flexibility so that the
L0txobject can initialise from the.sbdfile, creating theSbdMessageobject and a practically emptyEmailMessageobject.The only thing to note is that by doing this, we lose the logger GPS information which is only included in the transmission message and NOT the attachment.