andrew wrote:boscaiolo: most likely you are working with a standard graphics card driver that does not use all the memory your graphics card has. This can slow down things dramatically in recent versions of QCAD 2 since it uses double buffering. ...
# lspci | grep -i graphics
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02)
00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated Graphics Controller (rev 02)
# lsmod | grep intel
intel_agp 22900 1
agpgart 26620 3 drm,intel_agp
I am sure that qcad was functioning at normal speed a couple of weeks ago. I have updated various things in the interval, and am 90% sure that the change to qt4 happened during that update. Hence I attributed the slowdown to the qt version.
PS: Please elaborate on the QCAD 2.2 behavior that you think is "quirky", thanks.
The main alarming quirk was introduced after requests from users a few versions back. This is the persistent selection after a 'move'. Very often the object moved may be off-screen, so a subsequent attempt to delete elsewhere results in the loss of (sometimes large amounts of) data that is not obvious at the time, and may only be discovered days later. The persistent selection does not apply to the majority of edit actions. If it were universal, one would just get used to tapping 'tn' after every action, but when you do a series of, say, 10 manipulations in sequence and two of them happen to be 'move' it is not logical to have to treat these two differently. Far more rational would be to have a toggle to set persistent selection for those who prefer it, applying it to all edit actions. This would also be useful when one has to do a sequence of edits on one group of selections -- one could switch it on just for the duration of the manipulation.
I suspect that the other things that I see as quirky may be the result of limitations in the dxf format, and probably belong more on a wish-list that may not be able to be fulfilled.