--
You received this message because you are subscribed to the Google Groups "pyqtgraph" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyqtgraph+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/D7D8C7C8-266A-480C-967D-7E3E8660BD27%40alaska.edu.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/CA%2BnduTF8%3DXi20rGQxywn%3DPJYzx2B%2B_KqsR89qL4FOdzxD-RCXQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/CBED70C4-96C3-431C-BDE9-6379BB30E855%40alaska.edu.
On Oct 22, 2021, at 11:49 AM, Ognyan Moore <ognyan...@gmail.com> wrote:
Hi Israel,Good to hear from you. We had a lot of changes in 0.12.3 (one day we'll do a release with only a few changes), but I can't think of anything that would have broken mouse behavior.That said, just yesterday, I did merge an issue that does effect zooming, the issue was noticeable when the grid was displayed; but the issue it addresses is/was quite old.
If you can, I would try and give `master` branch a chance
, otherwise, if a minimum reproducible example is out of the question, I would attempt to do some kind of git bisect and see if you can zero in on the commit that started causing the problem to begin with.
On Oct 26, 2021, at 8:17 AM, Ognyan Moore <ognyan...@gmail.com> wrote:
Hi Israel,
We had another issue come in that might be relatedFor the "fun" of it, can you comment out the update method in ViewBox.py?
Depending on how easy it is to apply your patches to pyqtgraph within your example, could you try running a git-bisect from the master branch and see if you can zero in on the first problematic commit?
To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/CA%2BnduTEJ0hszKbwsvHPSZ8JH1g%3DL-vj%2BG8K73_iCF9q5qW9Tvg%40mail.gmail.com.
On Oct 26, 2021, at 8:17 AM, Ognyan Moore <ognyan...@gmail.com> wrote:
Hi Israel,
Depending on how easy it is to apply your patches to pyqtgraph within your example, could you try running a git-bisect from the master branch and see if you can zero in on the first problematic commit?
To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/CA%2BnduTEJ0hszKbwsvHPSZ8JH1g%3DL-vj%2BG8K73_iCF9q5qW9Tvg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/B5BC0B73-697D-452C-B3A9-14691ADCD362%40alaska.edu.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/CA%2BnduTGZqHtNcDW2Q6htJSXSKQ6c%3Dn7vQcDr%3DNZmj9eizBddPg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/CA%2BnduTGZqHtNcDW2Q6htJSXSKQ6c%3Dn7vQcDr%3DNZmj9eizBddPg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/34E45705-A9F8-4F91-9592-2C1CC8BD8373%40alaska.edu.