When attributes properties like min_alarm, max_alarm
are changed with jive, there are not taken immediately
into account by the device . The device server must be
restarted for the min_alarm parameter to be effective .
If the same modification is done through ATKPanel, the
device immediatly works with new parameters.
As we explain to users the Tango Configuration tool is
Jive and nothing else, it is not coherent to explain them,
that to have the properties modified they should use
atkpanel !
Analysis
jive should us the Device API if device is running
ans the DB API otherwise
Problem
When attributes properties like min_alarm, max_alarm are changed with jive, there are not taken immediately into account by the device . The device server must be restarted for the min_alarm parameter to be effective .
If the same modification is done through ATKPanel, the device immediatly works with new parameters.
As we explain to users the Tango Configuration tool is Jive and nothing else, it is not coherent to explain them, that to have the properties modified they should use atkpanel !
Analysis
jive should us the Device API if device is running ans the DB API otherwise
Reported by: buteau ( http://sf.net/u/buteau )
Original Ticket: "tango-cs/bugs/13":https://sourceforge.net/p/tango-cs/bugs/13