We use 'setpoint' in UI. Use it also for documentation and comments. No semantic change.

This commit is contained in:
Martin Měřinský 2017-03-06 13:36:42 +01:00 committed by Dirk Hohndel
parent dcf2542215
commit 95d5771513
9 changed files with 25 additions and 25 deletions

View file

@ -131,8 +131,8 @@ bool ConfigureDiveComputer::saveXMLBackup(QString fileName, DeviceDetails *detai
writer.writeTextElement("Dil3", dil3);
writer.writeTextElement("Dil4", dil4);
writer.writeTextElement("Dil5", dil5);
//
//Add set point values
//Add setpoint values
QString sp1 = QString("%1,%2")
.arg(QString::number(details->sp1.sp),
QString::number(details->sp1.depth));

View file

@ -501,7 +501,7 @@ static dc_status_t read_ostc3_settings(dc_device_t *device, DeviceDetails *m_dev
m_deviceDetails->dil4 = dil4;
m_deviceDetails->dil5 = dil5;
//Read set point Values
//Read setpoint Values
setpoint sp1;
setpoint sp2;
setpoint sp3;
@ -700,7 +700,7 @@ static dc_status_t write_ostc3_settings(dc_device_t *device, DeviceDetails *m_de
return rc;
EMIT_PROGRESS();
//write set point values
//write setpoint values
unsigned char sp1Data[2] = {
m_deviceDetails->sp1.sp,
m_deviceDetails->sp1.depth

View file

@ -54,7 +54,7 @@ static int handle_event_ver3(int code, const unsigned char *ps, unsigned int ps_
break;
case 0x0008:
// 4 byte time
// 2 byte gas set point 2
// 2 byte gas setpoint 2
skip = 6;
break;
case 0x000f: