tristan/kdeconnect-kde
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Don't use QString::null

Browse source
This commit is contained in:
Nicolas Fella 2019-02-03 02:00:36 +01:00
parent 2f6f4d9d65
commit 1f23fa27b2
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
core/backends/bluetooth/bluetoothdevicelink.cpp
View file

@ -79,7 +79,7 @@ void BluetoothDeviceLink::dataReceived()
//qCDebug(KDECONNECT_CORE) << "BluetoothDeviceLink dataReceived" << packet;
NetworkPacket packet(QString::null);
NetworkPacket packet((QString()));
NetworkPacket::unserialize(serializedPacket, &packet);
if (packet.type() == PACKET_TYPE_PAIR) {

2
core/backends/lan/landevicelink.cpp
View file

@ -117,7 +117,7 @@ void LanDeviceLink::dataReceived()
if (m_socketLineReader->bytesAvailable() == 0) return;
const QByteArray serializedPacket = m_socketLineReader->readLine();
NetworkPacket packet(QString::null);
NetworkPacket packet((QString()));
NetworkPacket::unserialize(serializedPacket, &packet);
//qCDebug(KDECONNECT_CORE) << "LanDeviceLink dataReceived" << serializedPacket;

2
core/backends/loopback/loopbackdevicelink.cpp
View file

@ -35,7 +35,7 @@ QString LoopbackDeviceLink::name()
bool LoopbackDeviceLink::sendPacket(NetworkPacket& input)
{
NetworkPacket output(QString::null);
NetworkPacket output((QString()));
NetworkPacket::unserialize(input.serialize(), &output);
//LoopbackDeviceLink does not need deviceTransferInfo