Paint Data is buggy - ill defined

[borondics]

What's wrong?

I have some not very well definable behaviour in Paint Data. I was recreating the documentation example for new screenshots and first I had a couple of crashes with segfault, so not very informative, although I reproduced it twice. Then, after creating a new workflow from scratch it started working but it visibly slows down every time I paint many points to the state that it keeps painting after the mouse is released.

How can we reproduce the problem?

Paint a lot of data (might depend on the computer how much a lot is) with different classes, just like in the help of the widget. Something like this

What's your environment?

• Operating system: MacOS 14.6.1
• Orange version: 3.39.0dev master
• How you installed Orange: manually from the master branch

[ales-erjavec]

... first I had a couple of crashes with segfault, ...

Can you open ~/Library/Logs/DiagnosticReports folder and look for Python-${DATE}-some-gibberish.ips file (with $DATE when this occurred if you still remember) open it and post the contents.

Then, after creating a new workflow from scratch it started working but it visibly slows down every time I paint many points to the state that it keeps painting after the mouse is released.

I cannot reproduce this. What version of PyQt and pyqtgraph do you have installed?

[borondics]

The Python crash files are not there in the logs...

I have:
pyqtgraph==0.13.7
AnyQt==0.2.0
PyQt6==6.7.1

[ales-erjavec]

.. first I had a couple of crashes with segfault, ...

Did you have Hierarchical clustering widget connected to the Paint widget somewhere downstream? I found this #6989 while trying to reproduce this.

visibly slows down every time I paint many points to the state that it keeps painting after the mouse is released.

Did you have other widgets connected downstream and had Send Automatically enabled? How many points exactly is many? 500? The widget is not exactly optimized but should handle 2000+ points