improper implementation of ros::Time::useSystemTime() about roscpp_core HOT 3 CLOSED

The function bool Time::useSystemTime() acts as a "getter" - not as a "setter" so it is fine as it is. (Maybe not named very intuitively.)

Assuming this resolves your "problem" I will go ahead and close the ticket. Please feel free to continue commenting on it.

from roscpp_core.

then what's the difference between bool Time::useSystemTime() and bool Time::isSystemTime() ?
and which function to call if we want to change to using Systemtime, where is the "setter" function? Time::init() ?

from roscpp_core.

what's the difference between bool Time::useSystemTime() and bool Time::isSystemTime()?

There is none - both methods do exactly the same.

which function to call if we want to change to using Systemtime, where is the "setter" function? Time::init()?

The choice between system time and sim time is being made based on the Clock. So there is no API you expect to simply switch between them. When sim time is enabled and clock messages are received they set the time (https://github.com/ros/ros_comm/blob/6b9efd56d6882d1c017152ba11a5780a1496b30b/clients/roscpp/src/libros/init.cpp#L255-L258) which then changes the state of the clock:

from roscpp_core.