mirror of
https://github.com/meshtastic/firmware.git
synced 2026-06-19 14:10:51 -04:00
beb268ff25
I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides.
I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop.
I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say.
This reverts commit 0d11331d18.
39 lines
1.2 KiB
C++
39 lines
1.2 KiB
C++
#pragma once
|
|
#include "MeshModule.h"
|
|
#include "Router.h"
|
|
|
|
/**
|
|
* Most modules are only interested in sending/receiving one particular portnum. This baseclass simplifies that common
|
|
* case.
|
|
*/
|
|
class SinglePortModule : public MeshModule
|
|
{
|
|
protected:
|
|
meshtastic_PortNum ourPortNum;
|
|
|
|
public:
|
|
/** Constructor
|
|
* name is for debugging output
|
|
*/
|
|
SinglePortModule(const char *_name, meshtastic_PortNum _ourPortNum) : MeshModule(_name), ourPortNum(_ourPortNum) {}
|
|
|
|
protected:
|
|
/**
|
|
* @return true if you want to receive the specified portnum
|
|
*/
|
|
virtual bool wantPacket(const meshtastic_MeshPacket *p) override { return p->decoded.portnum == ourPortNum; }
|
|
|
|
/**
|
|
* Return a mesh packet which has been preinited as a data packet with a particular port number.
|
|
* You can then send this packet (after customizing any of the payload fields you might need) with
|
|
* service->sendToMesh()
|
|
*/
|
|
meshtastic_MeshPacket *allocDataPacket()
|
|
{
|
|
// Update our local node info with our position (even if we don't decide to update anyone else)
|
|
meshtastic_MeshPacket *p = router->allocForSending();
|
|
p->decoded.portnum = ourPortNum;
|
|
|
|
return p;
|
|
}
|
|
}; |