Hi, >> - pace should sit close to speed, it's an equivalent > I agree, but to be honest, this won't change before releasing 1.9.0... 0:)
completely understandable. Nevertheless this battlefield should be addressed ASAP. Nathan already prepares something. > I have experienced some strange behavior with record view: I don't > have any specific clickpath, but I got the impression some times it > get stuck. True. There isn't always a proper, instant update of the view. Especially if you delete a record, the Active/Rest field has a quite long lifetime. > This makes sense. We should move into a logic where values get > calculated on the fly depending of data introduced instead of waiting > for user clicking "calculate" buttons. Right idea IMHO. In principle there are 3(+1) variables, but only 2 of them are independent. (+1 means pace is strongly correlated to speed). If two are given the others should be calculated on the fly. Additionally the inputs of those dependent variables should become locked. To unlock it one would have first to clear another one. (so maybe introduce a 'Clear' Button instead of the 'Calculate' one) > Ooops! I have just added this comment to ticket #71 (sorry, I wasn't > aware of it!) if this short circuit is going to break the internet we'll blame you, David ;) cu Arnd ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
