supply default values so we don't crash if nodes are missing in the boost::property_tree
adding const
removing an unused function. (in fact, it had no body. it had only the prototype in the header)
adding const
an xid device (xid1 or xid2) should definitely handle a call to query_base_timer. however, prior to this commit, if you tried it, you would get the result of base_device_t::query_base_timer (the 'empty' parent interface class), which is to always return INVALID_RETURN_VALUE
Merge branch 'master' of github.com:cedrus-opensource/xid_device_library
removing a now-obsolete comment
now there is only 1 centralized location where we house the logic for ajusting endianness of 4-char byte sequences to extract a number (and vice-versa)