search

aaronevers / indiprop

Automatically exported from code.google.com/p/indiprop
GNU General Public License v3.0
1 stars 2 forks source link

Busy status #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Indiprop should set local state to Busy whenever Set is issued (appears not to).

Original issue reported on code.google.com by edow...@lbti.org on 23 Mar 2013 at 7:14

GoogleCodeExporter commented 9 years ago 
You are correct, according to the INDI specification.  However, this is 
incorrect from a usability point of view.  Setting 'Busy' upon 'Set' by the 
client implies that the server has responded with a 'Busy' state notification, 
which isn't necessarily the case.  If you want the client to show the device as 
'Busy', set the state to 'Busy' at the server - this way all clients know that 
the device is busy.

Upon 'Set' indiprop sets the device UI hint to 'disabled' until it receives an 
appropriate response from the server.

Original comment by eve...@gmail.com on 23 Mar 2013 at 7:55

GoogleCodeExporter commented 9 years ago 
I agree with everything you say about Devices having responsibility to
report their status. However, since INDI is a shared "bus" architecture, I
consider the mere act of sending a command to a Device is tantamount to
making that Device go Busy. Just because the Device doesn't know yet the
command is on the way, other actors have the means to know if they care
(Clients can monitor other Client's "new" actions). And, more to the point
in this case, certainly the Client that sends the command already knows the
Device will be busy.

But if you don't want to do this, that's fine, it's not a major issue.

Original comment by edow...@lbti.org on 25 Mar 2013 at 3:25