Package: xdot Version: 1.0-1 Severity: normal Tags: upstream on exceptionally complex graphs that are displayed on extremely high resolutin screens, the refresh rate of xdot can be as low as two (2) SECONDS per frame. not two frames per second, two SECONDS per frame.
this provides a unique means of identifying an otherwise obscure bug. action is as follows: * load up ridiculously large graph on 3000x1800 (or greater) full-screen LCD * press and hold mouse * move mouse (to activate "display drag") * whilst STILL MOVING the mouse, LET GO of the button. what will happen is that the display will jump BACK to a FORMER (last updated) position, as opposed to leaving the display where the cursor is PRESENTLY located. this is understandable extremely annoying behaviour, as it requires an additional two (or greater) seconds of holding the mouse absolutely still, waiting for an otherwise unnecessary display-update in order that the last known prior location become the present location, such that, on release of the mouse, the bug will not result in the display jumping to an undesirable location. it is also understandable that given that most people do not view ridiculously complex graphs on ridiculously high resolution LCDs, that the bug may never have been encountered before. -- System Information: Debian Release: 8.1 APT prefers oldoldstable APT policy: (500, 'oldoldstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xdot depends on: ii gir1.2-gtk-3.0 3.22.26-2 ii graphviz 2.40.1-5+b2 ii python3-gi 3.30.1-2 ii python3-gi-cairo 3.30.1-2 pn python3:any <none> xdot recommends no packages. xdot suggests no packages. -- no debconf information
