On Wednesday 08 September 2010, Prasenjit Kapat wrote:
With that said, here is a difference in behavior, that we should resolve:
Hm, that might be a case in point that dev.copy() should duplicate the history
position, after all. Then situation 1 would be basically identical to
situation 2. On
Hi,
overall this specification looks good to me. I do think there are some aspects
which can safely be neglected for an initial implementation, however, in order
not to introduce too much complexity too soon. I'll point out those, and add a
few other comments.
On Tuesday 07 September 2010,
On Tuesday 07 September 2010, Thomas Friedrichsmeier wrote:
The idea to use a hash is certainly appealing, but I'm also reluctant to
add new hard dependencies. Using an optional dependency, sounds like
adding a lot of complexity, though. Qt also supports MD5 and SHA1, so
perhaps it's not too
Hi,
Since I am trying do this from scratch, let me try to chalk out the
intended features and expected caveats. So please comment with your
suggestion / objections.
A. a global history - all managed screen devices will share it.
B. ignore preview devices completely
C. a STATIC global switch
