Summary: | View Fit Results menu doesn't enable when a fit is created | ||
---|---|---|---|
Product: | [Applications] kst | Reporter: | Eli Fidler <eli> |
Component: | general | Assignee: | kst |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 1.x | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Eli Fidler
2006-12-13 22:10:54 UTC
Are you creating the fit via the RMB plot menu dialog? When I create one this way the View Fit Results menu is enabled... When I create via the datamanager, I get a deadlock... possibly related to 612802?? I'm creating them using the New Plugin menu option under Data. Creating them under the data manager works for me (there was a deadlock I fixed), but the menu is still disabled. It looks like the dataChanged() signal is not being emitted. I just tried to create a fit from the RMB menu and Kst crashes nastily. I appear to have broken that. Ok.. I fixed the crash, but the menu item is still disabled. I suppose it's possible that this only happens in my branch, although George thinks it should happen in trunk as well. Eli On Wednesday 13 December 2006 16:31, Adam Treat wrote: [bugs.kde.org quoted mail] Yes, when your deadlock fix is applied to trunk the bug reveals itself. Also, I don't get a crash when using the RMB menu in your branch. Instead, the proper curve is not detected by the fitdialog. Apparently this is due to some changes with the tags handling... I'll apply your deadlock fix to my local copy and go from there. BTW, I think your deadlock fix in hierarchy solves bug #135548 :) Should this be applied to trunk before the merge of your branch? SVN commit 613549 by treat: * And today is that lucky day... BUG:138776 M +1 -3 kst.cpp --- trunk/extragear/graphics/kst/src/libkstapp/kst.cpp #613548:613549 @@ -2172,12 +2172,10 @@ if (!onlyVisible || changeNptsDialog->isShown()) { changeNptsDialog->updateChangeNptsDialog(); } - if (!onlyVisible) { // FIXME: might want to make this sensible one day - updateDataDialogs(false); - } if (!onlyVisible || vectorSaveDialog->isShown()) { vectorSaveDialog->init(); } + updateDataDialogs(false); updateDataManager(onlyVisible); updateViewManager(onlyVisible); #ifdef BENCHMARK Change version to 1.x |