libicsneo/include/icsneo/device/tree/valuecan4
Paul Hollinsky e29d63b08c Add Keysight branding where applicable
Because there is now more than one "product name" per device
type, we have a concept of a "generic product name" which
singularly maps onto a device type.

This change comes with a few small breaking changes within
the C++ API:

DeviceType::GetDeviceTypeString has been renamed to
DeviceType::GetGenericProductName to denote that
the returned value is not device specific and
device->getProductName() is preferable.

The member function DeviceType::toString has been renamed
to DeviceType::getGenericProductName for the same reason.

The DeviceType std::ostream& operator<< has been removed
to avoid accidental use of the generic product name.
2021-04-12 19:01:43 -04:00
..
settings Support software controllable termination 2021-04-11 22:13:51 -04:00
valuecan4-1.h ValueCAN 4-2EL: Add communication over Ethernet 2020-09-14 12:35:43 -04:00
valuecan4-2.h Add Keysight branding where applicable 2021-04-12 19:01:43 -04:00
valuecan4-2el.h Add Keysight branding where applicable 2021-04-12 19:01:43 -04:00
valuecan4-2eleth.h ValueCAN 4-2EL: Add communication over Ethernet 2020-09-14 12:35:43 -04:00
valuecan4-2elusb.h ValueCAN 4-2EL: Add communication over Ethernet 2020-09-14 12:35:43 -04:00
valuecan4-4.h Add Keysight branding where applicable 2021-04-12 19:01:43 -04:00
valuecan4.h ValueCAN 4-2EL: Add communication over Ethernet 2020-09-14 12:35:43 -04:00
valuecan4industrial.h Add ValueCAN 4 Industrial 2020-09-14 12:45:32 -04:00
valuecan4industrialeth.h Add ValueCAN 4 Industrial 2020-09-14 12:45:32 -04:00
valuecan4industrialusb.h Add ValueCAN 4 Industrial 2020-09-14 12:45:32 -04:00