[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 #3 from Miguel Chavez Gamboa <miguel chavez gamboa gmail com>  2010-10-13 06:00:51 ---
(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 think its what you say, a circular signals-slot reactions (the slider changes
and the map zoom changes in reaction, then as the map zoom changed the slider
changes again and the loop is endless)

I can see this if I remove the 
 connect(ui->zoomSlider, SIGNAL(valueChanged(int)), theMap, SLOT(zoomView(int))
);
but keep the
 connect(theMap, SIGNAL(zoomChanged(int)), ui->zoomSlider, SLOT(setValue(int))
);

I does not freezes. This way I can get the slider updated when the
marblewidget's zoom changes, but I cannot zoom with the slider.

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