[Marble-bugs] [Bug 254000] MarbleWidget and Slider for the zoom causes the application to use 100% CPU.

[Miguel Chavez Gamboa]

https://bugs.kde.org/show_bug.cgi?id=254000





--- Comment #2 from Miguel Chavez Gamboa <miguel chavez gamboa gmail com>  2010-10-13 04:58:40 ---
(In reply to comment #1)
> Just a quick guess (didn't look into it in detail yet): Does changeSlider(int)
> cause another map->zoomView() call? Then bug 249628 could be related, because
> there'd be a circular connection that's not broken in MarbleWidget because of
> the off-by-one error.

I also think its a endless loop, and maybe related to the bug 249628.

I removed the animations, and before making the connection (signal->slot) of
the slider, i call:

slider->setValue(2000);
theMap->zoomView(2000);
..
connect( ..the signal connections.. );

And it works fine the first zoomView, after the signal connection, if i click
the Zoom-in button, the zoom changes from 2000 to 1000 and the app freezes.

I placed a qDebug() at the MarbleWidget::zoomView(...) and i got this:

ZomView newZoom: 2039
ZomView newZoom: 2038
ZomView newZoom: 2037
...
More output
...
ZomView newZoom: 1003
ZomView newZoom: 1002
ZomView newZoom: 1000
..here it freezes.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.