The buttons "start/stop" and "lock" are mutually exlusive (it does not make sense to have a locked engine if it's stopped). So we have two ways: 1) when we stop a locked engine, the lock flag must be reset. 2) when an engine is locked, it cannot be stopped.
If I think that the position of a locked engine is lost when the engine is stopped (this is not, indeed, a "pause" as you cannot resume it), then I prefer the second solution, in order to avoid an unwilling or wrong stop button pressing. In my opinion, it's far better that an user explicitly reset the lock status before he can stop the engine. But this is only my opinion, the behaviour can be changed. Bye. Alexander Wagner ha scritto: > Hi! > > Simple question: why does "lock to position" disable the > pause button? > > I start analysis in one game, then I lock the postion and > switch to another one. Why shouldn't I pause the analysis? > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
