From 4c2e1529c02bd72ec9662a04f856d9099f3f327d Mon Sep 17 00:00:00 2001 From: Anton Lundin Date: Fri, 13 Jul 2018 16:45:02 +0200 Subject: Fix configure bluetooth ostc's When we introduced the whole check for supported transports code, no one noticed that it broke configuring all ostc's over bluetooth. The configure code just used a placeholder model of OSTC 3 to get the right backend code. With the new supported transports model it errored out if you where trying to connect to a bluetooth enabled device, just because the original OSTC 3's wasn't bluetooth enabled. This switches the placeholder model over to a OSTC Plus which is both bluetooth, serial and ble capable, so the code works again. Signed-off-by: Anton Lundin --- desktop-widgets/configuredivecomputerdialog.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'desktop-widgets/configuredivecomputerdialog.cpp') diff --git a/desktop-widgets/configuredivecomputerdialog.cpp b/desktop-widgets/configuredivecomputerdialog.cpp index bceaa98f9..47eced724 100644 --- a/desktop-widgets/configuredivecomputerdialog.cpp +++ b/desktop-widgets/configuredivecomputerdialog.cpp @@ -1429,7 +1429,7 @@ void ConfigureDiveComputerDialog::on_DiveComputerList_currentRowChanged(int curr break; case 1: selected_vendor = "Heinrichs Weikamp"; - selected_product = "OSTC 3"; + selected_product = "OSTC Plus"; fw_upgrade_possible = true; break; case 2: -- cgit v1.2.3-70-g09d2