[okular] [Bug 382858] PDF form bug in displaying popdown boxes
https://bugs.kde.org/show_bug.cgi?id=382858 Uwe Stöhr changed: What|Removed |Added Platform|Manjaro |Microsoft Windows Status|NEEDSINFO |REPORTED OS|Linux |Microsoft Windows Resolution|WAITINGFORINFO |--- --- Comment #5 from Uwe Stöhr --- > I've just tested with the PDF you attached and the dropdown box works in > Okular What did you test? I took now the latest Windows nightly build (Okular master build 585) and it still doesn't work. Attached is a screenshot with Okular and for comparison with Adobe Reader. The bugs are: - The popdown box is incorrectly drawn. Its size was chosen to display all 3 entries of the list and in Adobe Reader it appears correctly with this size. Okular ignore the settings and display about 2 entries. - the combobox was designed so that no entry is preselected (Important that nobody feel discriminated). Okular ignores this as well and preselects the first entry. - the radio button still don't work, as you can see, in Okular one can check both radio buttons and the one for "female" is broken. I reported this separately as bug 382857 . -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382858] PDF form bug in displaying popdown and combo boxes
https://bugs.kde.org/show_bug.cgi?id=382858 Uwe Stöhr changed: What|Removed |Added Version|1.1.0 |1.11.3 Summary|PDF form bug in displaying |PDF form bug in displaying |popdown boxes |popdown and combo boxes -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382858] PDF form bug in displaying popdown and combo boxes
https://bugs.kde.org/show_bug.cgi?id=382858 --- Comment #6 from Uwe Stöhr --- Created attachment 133629 --> https://bugs.kde.org/attachment.cgi?id=133629&action=edit view in Okular 1.11 How it is displayed in Okular 1.11 on Windows -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382858] PDF form bug in displaying popdown and combo boxes
https://bugs.kde.org/show_bug.cgi?id=382858 --- Comment #7 from Uwe Stöhr --- Created attachment 133630 --> https://bugs.kde.org/attachment.cgi?id=133630&action=edit view in Adobe Reader How it is correctly displayed in Adobe Reader on Windows -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382857] PDF form bug in displaying dependent radiobuttons
https://bugs.kde.org/show_bug.cgi?id=382857 Uwe Stöhr changed: What|Removed |Added OS|Linux |Microsoft Windows Version|1.3.3 |1.11.3 Platform|Kubuntu Packages|Microsoft Windows --- Comment #3 from Uwe Stöhr --- The bug is still in latest Okular 1.11. I attached two screenshots, one with Okular and one with Adobe Reader. As you can see one can still check both radio buttons and the second one is broken. (the other 2 bugs you can see in the screenshots are already reported as bug 382858) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382857] PDF form bug in displaying dependent radiobuttons
https://bugs.kde.org/show_bug.cgi?id=382857 --- Comment #4 from Uwe Stöhr --- Created attachment 133631 --> https://bugs.kde.org/attachment.cgi?id=133631&action=edit view in Okular 1.11 How it is displayed in Okular 1.11 on Windows -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382857] PDF form bug in displaying dependent radiobuttons
https://bugs.kde.org/show_bug.cgi?id=382857 --- Comment #5 from Uwe Stöhr --- Created attachment 133632 --> https://bugs.kde.org/attachment.cgi?id=133632&action=edit view in Adobe Reader How it is correctly displayed in Adobe Reader on Windows -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382857] PDF form bug in displaying dependent radio buttons
https://bugs.kde.org/show_bug.cgi?id=382857 Uwe Stöhr changed: What|Removed |Added Summary|PDF form bug in displaying |PDF form bug in displaying |dependent radiobuttons |dependent radio buttons -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382864] wrong info about PDF backend
https://bugs.kde.org/show_bug.cgi?id=382864 --- Comment #10 from Uwe Stöhr --- Thus bug is still in Okular 1.11. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382859] Okular does not execute JavaScript of PDF forms
https://bugs.kde.org/show_bug.cgi?id=382859 Uwe Stöhr changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Uwe Stöhr --- The situation is now (Okular 1.11) better. Clicking the second push button in sec. 2.4 of the example PDF (attachment 106922), the JavaScript code is executed. So I think the bug can be marked as fixed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382863] Okular does not submit PDF form content
https://bugs.kde.org/show_bug.cgi?id=382863 --- Comment #1 from Uwe Stöhr --- The bug is still in Okular 1.11 (tested on Windows using the nightly build 585). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382860] Okular does not execute any basic PDF form action
https://bugs.kde.org/show_bug.cgi?id=382860 --- Comment #5 from Uwe Stöhr --- The bug is still in Okular 1.11 (tested on Windows using the nightly build 585). The improvement is that the button to show the form in fullscreen works now, the button to reset the form and to print it, are still not working. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 429635] New: PDF form bug - hyperlink not opened by push button
https://bugs.kde.org/show_bug.cgi?id=429635 Bug ID: 429635 Summary: PDF form bug - hyperlink not opened by push button Product: okular Version: 1.11.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: uwesto...@lyx.org Target Milestone: --- attachment 106922 is a PDF form I created with the latest pdflatex (attachment 106923 is its sourcecode). It fulfils the PDF form specification. In Okular 1.11 (Windows nightly build 585) the bug is: - open the PDF and go to sec. 2.4 - There click on the third button of the section result: nothing happens expected result: a website should be opened. This works correctly with Adobe Reader. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408530] New: error bars not correctly shown in plots
https://bugs.kde.org/show_bug.cgi?id=408530 Bug ID: 408530 Summary: error bars not correctly shown in plots Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@lyx.org Target Milestone: --- Created attachment 120752 --> https://bugs.kde.org/attachment.cgi?id=120752&action=edit plot showing the bug - open the attached example file - look at the plot: the error bars of the first data points are missing and I cannot find out why The Chi^2_red is however correctly calculated using also the undisplayed error bars. So it is a pure display bug but a nasty one since one cannot use the plot in papers, presentations etc. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408529] New: regression: cannot delete multiple cell contents at once
https://bugs.kde.org/show_bug.cgi?id=408529 Bug ID: 408529 Summary: regression: cannot delete multiple cell contents at once Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@lyx.org Target Milestone: --- Created attachment 120751 --> https://bugs.kde.org/attachment.cgi?id=120751&action=edit test case - open the attached file and try to delete in the first column the content of cell 2 to 8 result: this is impossible. Neither DEL, SHIFT +DEL or anything else works to delete. This is a regression to former LabPlot versions and very annoying. p.s. In the bug tracker I cannot specify the LabPlot version 2.5.0 or 2.6.0 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408533] New: wrong auto range for plots
https://bugs.kde.org/show_bug.cgi?id=408533 Bug ID: 408533 Summary: wrong auto range for plots Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@lyx.org Target Milestone: --- Created attachment 120754 --> https://bugs.kde.org/attachment.cgi?id=120754&action=edit example plot showing the bug - open the attached plot - look at the x-axis: it runs from 0 to 4000 but there are only data in the plot with up to x=1200 So the automatic range is determination is obviously broken. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408535] New: regression: wrong calculation of chi^2 reduced for fits
https://bugs.kde.org/show_bug.cgi?id=408535 Bug ID: 408535 Summary: regression: wrong calculation of chi^2 reduced for fits Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: grave Priority: NOR Component: backend Assignee: alexander.se...@web.de Reporter: uwesto...@lyx.org Target Milestone: --- Created attachment 120756 --> https://bugs.kde.org/attachment.cgi?id=120756&action=edit example plot The main task for me with LabPlot is curve fitting but in version 2.6 there is a bug leading to wrong calculations of the chi^2: - open the attached plot - recalculate the fit and look at the results: LP tells me I have a chi^2 reduced of 441. This is obviously wrong since the fit is not that bad. It looks like it is around 2. And indeed, when performing the same fit with another program I get a Chi^2 reduced of 1.9617. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408536] New: display bug in curve fitting dialog
https://bugs.kde.org/show_bug.cgi?id=408536 Bug ID: 408536 Summary: display bug in curve fitting dialog Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@lyx.org Target Milestone: --- Created attachment 120757 --> https://bugs.kde.org/attachment.cgi?id=120757&action=edit screenshot of the bug In LP 2.6. the curve fitting dialog looks strange, see attached. So some dialog elements are not properly displayed. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408537] New: impossible to insert several rows or columns at once
https://bugs.kde.org/show_bug.cgi?id=408537 Bug ID: 408537 Summary: impossible to insert several rows or columns at once Product: LabPlot2 Version: latest Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@lyx.org Target Milestone: --- One often needs to insert e.g. 3 rows to a spreadsheet. But LP 2.6 doesn't offer to insert them. One has to add them one by one. This is annoying if you need e.g. 10 new rows. Other programs offer to insert either one row or a certain number of rows. Of you choose the latter you can set the number of rows to be inserted. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408535] regression: wrong calculation of chi^2 reduced for fits
https://bugs.kde.org/show_bug.cgi?id=408535 --- Comment #1 from Uwe Stöhr --- Here is the fit result of MagicPlot for comparison: LAST FIT Data Points Number: 35 Fitted Curves Number: 1 Parameters Number: 2 Degrees of Freedom (DoF): 33 Data Total Sum of Squares (TSS): 6.4226e8 Weighting: Standard Error (w = 1 / stdErr^2) DATA INTERVALS >FromTo 0 1200 RESULTS Iterations: 5 Convergence: 1.8829e-13 Residual Sum of Squares (RSS, χ^2): 64.737 Reduced RSS: 1.9617 Residual Standard Deviation: 1.4006 Coefficient of Determination R^2: 1 Adjusted R^2: 1 FITTED CURVES Custom CurveFit curve A=557.4639±22.049 B=468.3198±26.5106 y(x) = A*exp(-B/x) FITTED PARAMETERS Parameter Fit curve A Fit curve B Value 557.4639468.3198 Std. Dev. 22.049 26.5106 FIT FORMULA WITH VALUES y(x) = 557.4639*exp(-468.3198/x) FIT FORMULA WITH VARIABLES y(x) = A*exp(-B/x) A = 557.4639 B = 468.3198 s_A = 22.049 s_B = 26.5106 CORRELATION MATRIX Parameter Fit curve A Fit curve B Fit curve A 1 0.9415 Fit curve B 0.9415 1 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408541] New: impossible to specify data range for fits
https://bugs.kde.org/show_bug.cgi?id=408541 Bug ID: 408541 Summary: impossible to specify data range for fits Product: LabPlot2 Version: latest Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@lyx.org Target Milestone: --- Created attachment 120760 --> https://bugs.kde.org/attachment.cgi?id=120760&action=edit screenshot from MagicPlot In many cases you only want to fit a subset of data in a plot. For example you have measurement values from x= 10 - 100 but you only want to fit the values from x= 30 - 80. This can b done by other programs like MagicPlot or Origin but not with LP. This feature is important because there are plenty of cases where you have e.g. 2 linear effects. So you have to fit in 2 data ranges. Attached is a screenshot I made with MagicPlot to illustrate what I mean. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408529] regression: cannot delete multiple cell contents at once
https://bugs.kde.org/show_bug.cgi?id=408529 --- Comment #1 from Uwe Stöhr --- OK, I see now that I can - select the cells - right-click on them and choose in the appearing context menu Selection -> Clear Selection So could you please add a shortcut for this function. E.g. Shift+Del? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408548] New: impossible to set range for calculations in spreadsheets
https://bugs.kde.org/show_bug.cgi?id=408548 Bug ID: 408548 Summary: impossible to set range for calculations in spreadsheets Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@lyx.org Target Milestone: --- I often have the case that I have to set e.g. cell 1 - 20 for one column to ln(i)*10 (i is the row number). In other programs I can do this but not in LP because when I try to do this, the formula is always applied to the whole column. But I only want it for row 1 to 20. So it would be useful if you could add this functionality by adding to the the context menu the feature Selection -> Fill Selection With -> Function values when one selects only cells. The function values will then only be applies to the selected cells. (When highlighting the whole column, this feature is already available in the context menu under Generate Data -> Function values .) -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394223] Support the preview of the fitting curve using the fit start values
https://bugs.kde.org/show_bug.cgi?id=394223 Uwe Stöhr changed: What|Removed |Added CC||uwesto...@lyx.org --- Comment #7 from Uwe Stöhr --- the preview is now enabled per default(In reply to Stefan Gerlach from comment #6) > the preview is now enabled per default. I cannot see this. Where do I have to enable the preview manually? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408537] impossible to insert several rows or columns at once
https://bugs.kde.org/show_bug.cgi?id=408537 --- Comment #2 from Uwe Stöhr --- Wow, that was fast! Many thanks. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408530] error bars not correctly shown in plots
https://bugs.kde.org/show_bug.cgi?id=408530 --- Comment #2 from Uwe Stöhr --- > the value for the first point is zero. Yes, this is purposely and I also don't want an error bar. Physics says it must be zero so there cannot be an error. > For the next points with energy = 320, 260, ... 560J no error bars are shown > - this is bug. Here we don't handle correctly the rows from 2 to 8 in the > spreadsheet having NANs. I'll fix this. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408541] impossible to specify data range for fits
https://bugs.kde.org/show_bug.cgi?id=408541 Uwe Stöhr changed: What|Removed |Added CC||uwesto...@web.de Resolution|NOT A BUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #2 from Uwe Stöhr --- > The button can be found on the right side in the fit options section. Now I found it after a hard search. Maybe the button can be made a bit larger and I propose to label it "Advanced". I mean the Recalculate button has also an icon AND a label so that you know immediately what the button is about. Therefore I reopened the bug as enhancement. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408541] label button for advanced fit options
https://bugs.kde.org/show_bug.cgi?id=408541 Uwe Stöhr changed: What|Removed |Added Summary|impossible to specify data |label button for advanced |range for fits |fit options -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408535] regression: wrong calculation of chi^2 reduced for fits
https://bugs.kde.org/show_bug.cgi?id=408535 Uwe Stöhr changed: What|Removed |Added CC||uwesto...@web.de --- Comment #3 from Uwe Stöhr --- > To do a weighted fit, you have to select "Instrumental" for > y-Weight and the error column in the dock widget. I cannot find this setting. What I did was: - setting the third column in the spreadsheet as y-error - in the advanced fitting dialog I checked "use given data errors" So why does this then not result in a weighted fit? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408535] regression: wrong calculation of chi^2 reduced for fits
https://bugs.kde.org/show_bug.cgi?id=408535 --- Comment #4 from Uwe Stöhr --- I sent you a private mail with the testing result of LP 2.7.RC3: I cannot test properly because of crashes. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408535] regression: wrong calculation of chi^2 reduced for fits
https://bugs.kde.org/show_bug.cgi?id=408535 Uwe Stöhr changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG --- Comment #5 from Uwe Stöhr --- OK, now I found it. To get a weighted fit one has to set that LP should really take the given error column. It would be very useful if this would be the default if there is an error column. Moreover the setting section "Weight" is by default collapsed and thus very hard to find. it should be unfolded by default like all other sections in the fit dialog. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408533] wrong auto range for plots
https://bugs.kde.org/show_bug.cgi?id=408533 Uwe Stöhr changed: What|Removed |Added CC||uwesto...@web.de --- Comment #3 from Uwe Stöhr --- > Did you create the fit maybe with data that also ranged from 0 to 4000 and > deleted some data leaving the data for x=0, ..., 1200 only without doing > another fit after this? No, input the data manually. The highest x value (the energy) is 1200. Therefore I am wondering why the fit goes up to 4000. In the fitting dialog I set the option to auto-range and I can see there that this means from 0..1200, see the attached screenshot. So I don't know where the fitting range up to 4000 came into play. I can also not find out where to change this, except of turning off auto-range. So maybe the bug is that the auto-range option for fits did not use the correct values? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408533] wrong auto range for plots
https://bugs.kde.org/show_bug.cgi?id=408533 --- Comment #4 from Uwe Stöhr --- Created attachment 121282 --> https://bugs.kde.org/attachment.cgi?id=121282&action=edit screenshot of fitting settings -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408536] display bug in curve fitting dialog
https://bugs.kde.org/show_bug.cgi?id=408536 Uwe Stöhr changed: What|Removed |Added CC||uwesto...@web.de --- Comment #1 from Uwe Stöhr --- Created attachment 121405 --> https://bugs.kde.org/attachment.cgi?id=121405&action=edit screenshot of LP 2.7 RC5 The bug is now fixed in RC5, Many thanks! -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408536] display bug in curve fitting dialog
https://bugs.kde.org/show_bug.cgi?id=408536 Uwe Stöhr changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394029] Auto x/y-range keeps constant
https://bugs.kde.org/show_bug.cgi?id=394029 --- Comment #3 from Uwe Stöhr --- This issue remains in LP 2.7 RC5: When I explicitly change the x-range in a plot and keep the y-range on AUTO, I expect that the y-range will automatically be adjusted to the y-range in the given x-range. So in my example changing the x-range to 1..30 should automatically change the y-range to 1..30 as well since 1..100 is senseless because there is no y > 30 for the given x-range. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408533] wrong auto range for plots
https://bugs.kde.org/show_bug.cgi?id=408533 Uwe Stöhr changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Uwe Stöhr --- Since the bug is no longer reproducible, I'll close it. The bug was caused by a wrong range for the fit. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 410039] New: OPJ import does not recognize fit plots
https://bugs.kde.org/show_bug.cgi?id=410039 Bug ID: 410039 Summary: OPJ import does not recognize fit plots Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: backend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- Created attachment 121647 --> https://bugs.kde.org/attachment.cgi?id=121647&action=edit Origin file testcase - import the attached OPJ file It consists of 6 fit plats (linear fits). result: I get 6 xy-curves and no fit plots. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 400741] New: Properties explorer disappears
https://bugs.kde.org/show_bug.cgi?id=400741 Bug ID: 400741 Summary: Properties explorer disappears Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- Created attachment 116122 --> https://bugs.kde.org/attachment.cgi?id=116122&action=edit screenshot of the problem - start LabPlot 2.6 - click in the toolbar on the button "Properties Explorer" to suppress its view - now click the button again to make the explorer visible again result: there is only a white and empty field shown instead of the explorer -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 400742] New: enhancement: automatically adapt image format
https://bugs.kde.org/show_bug.cgi?id=400742 Bug ID: 400742 Summary: enhancement: automatically adapt image format Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- In terms of working speed I see room of improvement. An example: - start LabPlot - create a new spreadsheet result: the number format is by default: x,yy+ezz This is in my opinion not the most used format and should just be a float with 4 digits by default: x, However the function to fill a column with row numbers is commonly used. In this case the number formal of the row should automatically be set to float where the empty digits are not shown or to integer because when I fill the column with integer row numbers, another number format doesn't make sense. In case I apply a formula on the row numbers the number format should automatically be changed to float with 4 shown digits. This would speed up my work flow a lot. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394223] Support the preview of the fitting curve using the fit start values
https://bugs.kde.org/show_bug.cgi?id=394223 Uwe Stöhr changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|RESOLVED|REOPENED --- Comment #3 from Uwe Stöhr --- > LabPlot now supports preview with the given start values when enabling the > "preview" option. Not with he build you sent me: - create a new table with 2 columns - fill the table columns with row numbers - create a new custom fit - use as fit function this one a*x - set fit interval x:10 - 25 (what is the difference between the fit and the evaluation interval? Please add tooltips to explain this to the user) - enable the preview option - set parameter a to '2' result: I expect to see the function 2*x but nothing is shown. I found a workaround. one must right click in the project explorer on the fit and there check visible then subsequently select visible again. The bug is the LP shows you that the fit is visible in the context menu while it is not. Thus by making it unvisible and then visible again it is really shown. Note also that the default number format for the fit interval uses 6 visible digits. This is no common use case, at least reduce it to 4 digits. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 400747] New: Cannot enter non-integer start value for custom fit
https://bugs.kde.org/show_bug.cgi?id=400747 Bug ID: 400747 Summary: Cannot enter non-integer start value for custom fit Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- - create a new table with 2 columns - fill the table columns with row numbers - create a new custom fit - use as fit function this one a*x^2 - enable the preview option - try to set the start value for the parameter a to '-1' or to '1.1" result: only integers are allowed as start value. But this not sufficient for many use cases. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 400748] New: missing autoscale for x-axis of fit plots
https://bugs.kde.org/show_bug.cgi?id=400748 Bug ID: 400748 Summary: missing autoscale for x-axis of fit plots Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- - create a new table with 2 columns - fill the table columns with row numbers - create a new custom fit - use as fit function this one a*x - set fit and evaluation interval x:10 - 25 - set start parameter a to '2' - calculate the fit result: the x-axis of the diagram is still 0 - 100 But since I only fitted and evaluated from 10 - 25 the x-axis scale should automatically be set to the evaluation interval plus 10%. So in my case to 9 - 27.5. This would speed up the work flow a lot because since I explicitly set an evaluation interval I tell LP that i am interested in this interval. I can later chance the x-axis if i really need this but in the vast majority of the cases I need the evaluation interval to be drawn. Note also: What is the difference between the fit and the evaluation interval? Please add tooltips to explain this to the user. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 400749] New: x-axis interval mangles the diagram display
https://bugs.kde.org/show_bug.cgi?id=400749 Bug ID: 400749 Summary: x-axis interval mangles the diagram display Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- Created attachment 116126 --> https://bugs.kde.org/attachment.cgi?id=116126&action=edit screenshot of the problem - create a new table with 2 columns - fill the table columns with row numbers - create a new custom fit - use as fit function this one a*x - set fit and evaluation interval x:10 - 25 - set start parameter a to '2' - calculate the fit the x-axis runs from 0 - 100 (see also bug 400748). I want to change the x-axis to run from 10 - 25, therefore - click in the plot diagram on the x-axis and set there '10' as start and '25' as end value result: the x-axis does no longer use the full width of the diagram, see the attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 400742] enhancement: automatically adapt number format
https://bugs.kde.org/show_bug.cgi?id=400742 Uwe Stöhr changed: What|Removed |Added Summary|enhancement: automatically |enhancement: automatically |adapt image format |adapt number format -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394223] Support the preview of the fitting curve using the fit start values
https://bugs.kde.org/show_bug.cgi?id=394223 Uwe Stöhr changed: What|Removed |Added Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 Resolution|WORKSFORME |--- --- Comment #5 from Uwe Stöhr --- The bug is now fixed but the option to preview the fit option should be enabled by default. This is a very useful new feature and I am sure also other users don't like to enable this option for every fit manually. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 400747] Cannot enter non-integer start value for custom fit
https://bugs.kde.org/show_bug.cgi?id=400747 Uwe Stöhr changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Uwe Stöhr --- This is now fixed in 2.6RC2. Many thanks. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 400741] Properties explorer disappears
https://bugs.kde.org/show_bug.cgi?id=400741 --- Comment #2 from Uwe Stöhr --- This problem is still in 2.6.0RC2. I found a workaround: Just click in the project explorer and the properties explorer becomes visible immediately. So it seems to be a simple signal problem for the Qt widget for the toolbar button. I mean the bug does not appear for the project explorer toolbar button. > This is most probably caused by the animation we added for the dock widgets. I don't think this is the problem but nevertheless I don't see why e.g. hiding a dock widget must be animated. Therefore please remove this if it could make problems. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 400741] Properties explorer disappears
https://bugs.kde.org/show_bug.cgi?id=400741 Uwe Stöhr changed: What|Removed |Added CC||stefan.gerlach@uni-konstanz ||.de -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 400749] x-axis interval mangles the diagram display
https://bugs.kde.org/show_bug.cgi?id=400749 Uwe Stöhr changed: What|Removed |Added CC||stefan.gerlach@uni-konstanz ||.de --- Comment #1 from Uwe Stöhr --- Still in 2.6.0RC2. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 414475] New: cannot login to invent.kde.org using gitlab account
https://bugs.kde.org/show_bug.cgi?id=414475 Bug ID: 414475 Summary: cannot login to invent.kde.org using gitlab account Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: uwesto...@web.de Target Milestone: --- I want to contribute to the KDE project LabPlot. It moved recently to Gitlab. Therefore I created a Gitlab account and con log in successfully. But I cannot login to https://invent.kde.org/users/sign_in On the login site I can switch between KDE identity and standard login. I choose standard login to login using my Gitlab account. But this doesn't work. When using the credentials I used to create this bug report to login via the KDE identity account, it also doesn't work. So I see 2 issues: - login must be possible using a normal GitLab account - login to https://bugs.kde.org should work for all ***https://***.kde.org pages -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 414475] cannot login to invent.kde.org using gitlab account
https://bugs.kde.org/show_bug.cgi?id=414475 --- Comment #3 from Uwe Stöhr --- Created attachment 124105 --> https://bugs.kde.org/attachment.cgi?id=124105&action=edit screenshot of the 2 login methods -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 414475] cannot login to invent.kde.org using gitlab account
https://bugs.kde.org/show_bug.cgi?id=414475 Uwe Stöhr changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #2 from Uwe Stöhr --- > the issue is that you need a KDE Identity to log into invent.kde.org. This does not solve the issue: https://invent.kde.org/users/sign_in allows you to login in 2 ways, one with the KDE identity and one with the GitLab identity, see the attached screenshot. So I want to login using thee GitLab account. if this is not possible, please remove this from the login page or at least explain the users what "Standard" login means on the login page. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 414673] New: support to login to invent.kde.org using U2F
https://bugs.kde.org/show_bug.cgi?id=414673 Bug ID: 414673 Summary: support to login to invent.kde.org using U2F Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: uwesto...@lyx.org Target Milestone: --- invent.kde.org is now at GitLab. However, in contrary to GitLab, the KDE identity does not support 2 factor authentication via hardware. I can login to GitLab using e.g. the open-source Solo key. Since most of the major developer platforms are offering webauthn like FIDO2, kde.org should to. At the moment KDE is not even listed here: https://www.dongleauth.info/#developer -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 414475] cannot login to invent.kde.org using gitlab account
https://bugs.kde.org/show_bug.cgi?id=414475 Uwe Stöhr changed: What|Removed |Added CC||uwesto...@lyx.org --- Comment #5 from Uwe Stöhr --- Thanks Nicolás.(In reply to Nicolás Alvarez from comment #4) > We have now removed the "standard login" option. Thanks Nicolás. Unfortunately the KDE identity does not yet support the same login features as GitLab. I opened therefore bug 414673 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 382859] Okular does not execute JavaScript of PDF forms
https://bugs.kde.org/show_bug.cgi?id=382859 Uwe Stöhr changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- CC||uwesto...@web.de --- Comment #4 from Uwe Stöhr --- (In reply to Nate Graham from comment #3) > Was this fully resolved with... I just checked with Okular 18.04 and the problem persists. See my initial comment to reproduce the bug. The pus button executes JavaScript but the button is not clickable in Okular 18.04. On Adobe Reader i can click the button and the JavaScript is executed. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 386800] Custom fitting often fails
https://bugs.kde.org/show_bug.cgi?id=386800 Uwe Stöhr changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #20 from Uwe Stöhr --- This bug is not fixed in the latest available LabPlot version. > If you can provide the information requested in comment #14, please add it. OK: > Which values for a,b,c do you expect for best fitting you data? See the screen shot I once attached with a correct fit: https://bugsfiles.kde.org/attachment.cgi?id=108823 > the data columns are not restored when opening your project. What happens > when you select the x- and y-column correctly? I don't know what you mean. I created the file using LabPlot so there must be another bug that columns are not restored. Is there a new LabPlot build available to test? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394025] New: Crash when deleting spreadsheet
https://bugs.kde.org/show_bug.cgi?id=394025 Bug ID: 394025 Summary: Crash when deleting spreadsheet Product: LabPlot2 Version: 2.4.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- Created attachment 112517 --> https://bugs.kde.org/attachment.cgi?id=112517&action=edit LabPlot test file - use the attached LabPlot file - select the spreadsheet number 2 in the explorer tree, right click on it and choose in the appearing context menu "Delete" result: crash -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387610] Crash on resetting toolbars
https://bugs.kde.org/show_bug.cgi?id=387610 --- Comment #1 from Uwe Stöhr --- The crash is still in the latest LP 2.5 build from Stefan. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394025] Crash when deleting spreadsheet
https://bugs.kde.org/show_bug.cgi?id=394025 Uwe Stöhr changed: What|Removed |Added Version|2.4.0 |latest -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394025] Crash when deleting spreadsheet
https://bugs.kde.org/show_bug.cgi?id=394025 --- Comment #1 from Uwe Stöhr --- This bug is also in LP 2.5RC17 Stefan just sent me. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 386800] Custom fitting often fails
https://bugs.kde.org/show_bug.cgi?id=386800 Uwe Stöhr changed: What|Removed |Added Resolution|WORKSFORME |--- Status|NEEDSINFO |CONFIRMED --- Comment #22 from Uwe Stöhr --- > The parameter a is very sensitive. The fit works for me using start values > closer to the result (b=2, a=.05, c=2). ;-) Well, people use LabPlot because they don't yet the solution. using 1 for all 3 parameters is sensible because one can expect that the solution will have positive values and that b and c won't be very high. However, I restarted now from scratch using RC17 and this recipe: - create a new table with 2 columns - fill the table columns with row numbers - create a new custom fit - use as fit function this one exp(b*sin(a*x))+c - set fit interval x:10 - 25 - set as start value for all parameters "1" result: one doesn't get a fit curve What is missing is that LabPlot does not draw the cureve for A=b=c=1 immediately, meaning even before starting the calculation of the fit. Other programs like MagicPlot do this since it helps a lot to see if the start parameters are sensible. With RC17 the fitting result are now correct but as long as LabPlot does not draw the fit curve with the given start parameters, the problem is not fixed in my opinion. Btw. with RC17 LabPlot does no longer show any fit curve. I'll open new bug reports now. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394026] New: regression: changing axis range not applied
https://bugs.kde.org/show_bug.cgi?id=394026 Bug ID: 394026 Summary: regression: changing axis range not applied Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- - create a new table with 2 columns - fill the table columns with row numbers - highlight both columns and create a new custom fit in new fit in new worksheet - try to change the x-axis to see the part form x= 10..25 result: this fails. You can enter 10 as start for x or whatever but nothing changes. There is no apply button to apply the changed value or so. But checking/unchecking the AutoFit option is applied immediately, so the bug is that changes to values are not applied. Regression to former 2.5 RC versions. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394028] New: fit curve looses color
https://bugs.kde.org/show_bug.cgi?id=394028 Bug ID: 394028 Summary: fit curve looses color Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- - create a new table with 2 columns - fill the table columns with row numbers - highlight both columns and create a new custom fit in new fit in new worksheet - use as fit function this one a*x^2+b - set fit range x=10..25 - set as start value for all parameters "1" result: the fit curve is shown as blue line which is good to distinguish it from the base curve - now uncheck the "visible" option and check it again result: the fit curve has now the color black. So the color is lost. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394029] New: Auto x/y-range keeps constant
https://bugs.kde.org/show_bug.cgi?id=394029 Bug ID: 394029 Summary: Auto x/y-range keeps constant Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- - create a new table with 2 columns - fill the table columns with row numbers - highlight both columns and create a new custom fit in new fit in new worksheet - in the plot properties change the x-Range from "Auto" to x=1..30 result: the change is not applied unless one presses Enter. This is a regression, see bug 394026. The bug here is, however, that the y-Range is still in Auto. But as once changed the x-range, I expect the y-Range to change accordingly. But here it remains at y=1..100. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387853] New: missing themes
https://bugs.kde.org/show_bug.cgi?id=387853 Bug ID: 387853 Summary: missing themes Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- - use the menu Settings > Configure labplot2 - go to Worksheet and try there to set a theme result: there is no theme to choose from. This happens for my and Stefan's build. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387302] Missing Unicode support in fit result window
https://bugs.kde.org/show_bug.cgi?id=387302 --- Comment #1 from Uwe Stöhr --- Created attachment 109346 --> https://bugs.kde.org/attachment.cgi?id=109346&action=edit patch The attached patch fixes the bug for me and also the Unicode warnings I reported in bug 387118 and bug 387196. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 386792] LabPlot 2.5RC2 crashes when starting without admin privileges
https://bugs.kde.org/show_bug.cgi?id=386792 Uwe Stöhr changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Uwe Stöhr --- (In reply to Uwe Stöhr from comment #2) > This bug vanished in the meantime. I'll keep it open until I could test that > it is gone also with a build from Stefan. It is also gone in Stefan's Build -> Closing FIXED. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387859] New: function override warnings in Column.h
https://bugs.kde.org/show_bug.cgi?id=387859 Bug ID: 387859 Summary: function override warnings in Column.h Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: backend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- I get: 1>C:\CraftRoot\labplot\src\backend/core/column/Column.h(101): warning C4373: 'Column::setValueAt': virtual function overrides 'AbstractColumn::setValueAt', previous versions of the compiler did not override when parameters only differed by const/volatile qualifiers 1> C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(183): note: see declaration of 'AbstractColumn::setValueAt' 1>C:\CraftRoot\labplot\src\backend/core/column/Column.h(104): warning C4373: 'Column::setIntegerAt': virtual function overrides 'AbstractColumn::setIntegerAt', previous versions of the compiler did not override when parameters only differed by const/volatile qualifiers 1> C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(186): note: see declaration of 'AbstractColumn::setIntegerAt' -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387860] New: linker and loss of data warnings with OriginProjectParser
https://bugs.kde.org/show_bug.cgi?id=387860 Bug ID: 387860 Summary: linker and loss of data warnings with OriginProjectParser Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: backend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- I get: 3>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(299): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data 3>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(299): warning C4267: 'initializing': conversion from 'size_t' to 'const int', possible loss of data 3>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(597): warning C4267: 'initializing': conversion from 'size_t' to 'unsigned int', possible loss of data and also: 3>ImportOpj.obj : warning LNK4006: "class QString __cdecl strreverse(class QString const &)" (?strreverse@@YA?AVQString@@AEBV1@@Z) already defined in OriginProjectParser.obj; second definition ignored -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387861] New: argument truncation warnings in CartesianPlotLegend
https://bugs.kde.org/show_bug.cgi?id=387861 Bug ID: 387861 Summary: argument truncation warnings in CartesianPlotLegend Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: backend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- I get: 3>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlotLegend.cpp(114): warning C4305: 'argument': truncation from 'double' to 'const float' 3>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlotLegend.cpp(115): warning C4305: 'argument': truncation from 'double' to 'const float' 3>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlotLegend.cpp(116): warning C4305: 'argument': truncation from 'double' to 'const float' 3>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlotLegend.cpp(117): warning C4305: 'argument': truncation from 'double' to 'const float' 3>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlotLegend.cpp(118): warning C4305: 'argument': truncation from 'double' to 'const float' 3>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlotLegend.cpp(119): warning C4305: 'argument': truncation from 'double' to 'const float' -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387862] New: argument truncation warning in CartesianPlot
https://bugs.kde.org/show_bug.cgi?id=387862 Bug ID: 387862 Summary: argument truncation warning in CartesianPlot Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: backend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- I get: 3>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlot.cpp(2895): warning C4838: conversion from 'double' to 'float' requires a narrowing conversion 3>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlot.cpp(2895): warning C4305: 'initializing': truncation from 'double' to 'float' -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387863] New: Unicode warnings for RandomValuesDialog
https://bugs.kde.org/show_bug.cgi?id=387863 Bug ID: 387863 Summary: Unicode warnings for RandomValuesDialog Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- Created attachment 109347 --> https://bugs.kde.org/attachment.cgi?id=109347&action=edit proposed patch I get many Unicode warnings. Attached is a patch. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387196] conditional expression is constant warnings in XYFitCurveDock
https://bugs.kde.org/show_bug.cgi?id=387196 Uwe Stöhr changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Uwe Stöhr --- This bug was fixed today. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387863] Unicode warnings for RandomValuesDialog
https://bugs.kde.org/show_bug.cgi?id=387863 Uwe Stöhr changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Uwe Stöhr --- Fixed: https://github.com/KDE/labplot/commit/e4b556192c647aae3d78832f9e26428a9225b45a -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387877] New: last main window size is not stored
https://bugs.kde.org/show_bug.cgi?id=387877 Bug ID: 387877 Summary: last main window size is not stored Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- - open LabPlot and move its main window e.g. to the lower left of your screen - close LabPlot - open LabPlot again result: the main window does not have the size and the position you used the last time. All other programs I have installed store the size/position. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387118] loss of data warnings with XYFitCurve
https://bugs.kde.org/show_bug.cgi?id=387118 --- Comment #7 from Uwe Stöhr --- Now I get only these: 1>C:\CraftRoot\labplot\src\backend/core/column/Column.h(101): warning C4373: 'Column::setValueAt': virtual function overrides 'AbstractColumn::setValueAt', previous versions of the compiler did not override when parameters only differed by const/volatile qualifiers 1> C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(183): note: see declaration of 'AbstractColumn::setValueAt' 1>C:\CraftRoot\labplot\src\backend/core/column/Column.h(104): warning C4373: 'Column::setIntegerAt': virtual function overrides 'AbstractColumn::setIntegerAt', previous versions of the compiler did not override when parameters only differed by const/volatile qualifiers 1> C:\CraftRoot\labplot\src\backend/core/AbstractColumn.h(186): note: see declaration of 'AbstractColumn::setIntegerAt' 1>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\XYFitCurve.cpp(1779): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data 1>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\XYFitCurve.cpp(1780): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data 1>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\XYFitCurve.cpp(1782): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387859] function override warnings in Column.h
https://bugs.kde.org/show_bug.cgi?id=387859 Uwe Stöhr changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Uwe Stöhr --- Fixed with: https://commits.kde.org/labplot/c6354c94f2946bf83ab42f6b853d70ab8deff5fe -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387880] New: deprecated functions in LiveDataSource
https://bugs.kde.org/show_bug.cgi?id=387880 Bug ID: 387880 Summary: deprecated functions in LiveDataSource Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: backend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- I get: 1>C:\CraftRoot\labplot\src\backend\datasources\LiveDataSource.cpp(695): warning C4995: 'ParityError': name was marked as #pragma deprecated 1>C:\CraftRoot\labplot\src\backend\datasources\LiveDataSource.cpp(696): warning C4995: 'FramingError': name was marked as #pragma deprecated 1>C:\CraftRoot\labplot\src\backend\datasources\LiveDataSource.cpp(697): warning C4995: 'BreakConditionError': name was marked as #pragma deprecated -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387331] loss of data warnings in Column
https://bugs.kde.org/show_bug.cgi?id=387331 --- Comment #1 from Uwe Stöhr --- Now only these remain: 1>C:\CraftRoot\labplot\src\backend\core\column\Column.cpp(855): warning C4127: conditional expression is constant 1>C:\CraftRoot\labplot\src\backend\core\column\Column.cpp(859): warning C4127: conditional expression is constant 1>C:\CraftRoot\labplot\src\backend\core\column\Column.cpp(867): warning C4127: conditional expression is constant 1>C:\CraftRoot\labplot\src\backend\core\column\Column.cpp(871): warning C4127: conditional expression is constant 1>C:\CraftRoot\labplot\src\backend\core\column\Column.cpp(931): warning C4127: conditional expression is constant -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387331] loss of data warnings in Column
https://bugs.kde.org/show_bug.cgi?id=387331 Uwe Stöhr changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED --- Comment #3 from Uwe Stöhr --- Strange because now I get this: 1>C:\CraftRoot\labplot\src\backend\core\column\Column.cpp(1196): warning C4714: function 'QString QString::trimmed(void) &&' marked as __forceinline not inlined 1> C:\Qt\Qt5.9.3\5.9.3\msvc2015_64\include\QtCore/qstring.h(407): note: see declaration of 'QString::trimmed' -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387331] loss of data warnings in Column
https://bugs.kde.org/show_bug.cgi?id=387331 --- Comment #5 from Uwe Stöhr --- > Something we can not fix ourself: Thank you for this link. This helps me with other projects where i get the same warnings. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387860] linker and loss of data warnings with OriginProjectParser
https://bugs.kde.org/show_bug.cgi?id=387860 Uwe Stöhr changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- --- Comment #2 from Uwe Stöhr --- Now I get these warnings: 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(227): warning C4456: declaration of 'matrix' hides previous local declaration 1> C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(224): note: see declaration of 'matrix' 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(311): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(583): warning C4456: declaration of 'matrix' hides previous local declaration 1> C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(579): note: see declaration of 'matrix' -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387110] loss of data warnings with ImportOpj
https://bugs.kde.org/show_bug.cgi?id=387110 Uwe Stöhr changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Uwe Stöhr --- ImportOpj was removed today. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387862] argument truncation warning in CartesianPlot
https://bugs.kde.org/show_bug.cgi?id=387862 Uwe Stöhr changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- --- Comment #2 from Uwe Stöhr --- Now I get: 1>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlot.cpp(1310): warning C4456: declaration of 'curve' hides previous local declaration 1> C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlot.cpp(1302): note: see declaration of 'curve' 1>C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlot.cpp(1335): warning C4456: declaration of 'curve' hides previous local declaration 1> C:\CraftRoot\labplot\src\backend\worksheet\plots\cartesian\CartesianPlot.cpp(1328): note: see declaration of 'curve' -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387860] linker and loss of data warnings with OriginProjectParser
https://bugs.kde.org/show_bug.cgi?id=387860 Uwe Stöhr changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- --- Comment #4 from Uwe Stöhr --- I am sorry to report that I now get now other warnings: 1>C:\CraftRoot\labplot\liborigin/OriginFile.h(80): warning C4625: 'OriginFile': copy constructor was implicitly defined as deleted 1>C:\CraftRoot\labplot\liborigin/OriginFile.h(80): warning C4626: 'OriginFile': assignment operator was implicitly defined as deleted 1>C:\CraftRoot\labplot\src\backend/datasources/projects/OriginProjectParser.h(69): warning C4625: 'OriginProjectParser': copy constructor was implicitly defined as deleted 1>C:\CraftRoot\labplot\src\backend/datasources/projects/OriginProjectParser.h(69): warning C5026: 'OriginProjectParser': move constructor was implicitly defined as deleted 1>C:\CraftRoot\labplot\src\backend/datasources/projects/OriginProjectParser.h(69): warning C4626: 'OriginProjectParser': assignment operator was implicitly defined as deleted 1>C:\CraftRoot\labplot\src\backend/datasources/projects/OriginProjectParser.h(69): warning C5027: 'OriginProjectParser': move assignment operator was implicitly defined as deleted 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(367): warning C4365: 'argument': conversion from 'int' to 'unsigned __int64', signed/unsigned mismatch 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(404): warning C4242: 'argument': conversion from 'int' to 'char', possible loss of data 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(412): warning C4365: 'argument': conversion from 'int' to 'unsigned __int64', signed/unsigned mismatch 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(452): warning C4365: 'argument': conversion from 'int' to 'unsigned __int64', signed/unsigned mismatch 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(513): warning C4365: 'argument': conversion from 'int' to 'unsigned __int64', signed/unsigned mismatch 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(534): warning C4365: 'argument': conversion from 'int' to 'unsigned __int64', signed/unsigned mismatch 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(555): warning C4365: 'argument': conversion from 'int' to 'unsigned __int64', signed/unsigned mismatch 1>C:\CraftRoot\labplot\src\backend\datasources\projects\OriginProjectParser.cpp(613): warning C4365: 'argument': conversion from 'int' to 'unsigned __int64', signed/unsigned mismatch -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387860] linker and loss of data warnings with OriginProjectParser
https://bugs.kde.org/show_bug.cgi?id=387860 --- Comment #5 from Uwe Stöhr --- Ah I get them because the last time I compiled with level 4 and now with /Wall. However the mismatch warnings should be fixes in my opinion. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387962] New: wrong CMake compiler option
https://bugs.kde.org/show_bug.cgi?id=387962 Bug ID: 387962 Summary: wrong CMake compiler option Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- running CMake I get for every build target the additional option -fvisibility=default This leads to a compiler warning: 1>cl : Command line warning D9002: ignoring unknown option '-fvisibility=default' So if -fvisibility=default is not necessary for gcc and MinGw, it should be removed. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387963] New: signed/unsigned mismatch warnings for OriginFile
https://bugs.kde.org/show_bug.cgi?id=387963 Bug ID: 387963 Summary: signed/unsigned mismatch warnings for OriginFile Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: backend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- (The bug tracker should get a new component "liborigin".) I get: 1>c:\craftroot\labplot\liborigin\OriginFile.h(80): warning C4625: 'OriginFile': copy constructor was implicitly defined as deleted 1>c:\craftroot\labplot\liborigin\OriginFile.h(80): warning C4626: 'OriginFile': assignment operator was implicitly defined as deleted 1>C:\CraftRoot\labplot\liborigin\OriginFile.cpp(57): warning C4365: 'initializing': conversion from 'long' to 'unsigned int', signed/unsigned mismatch 1>C:\CraftRoot\labplot\liborigin\OriginFile.cpp(60): warning C4365: '=': conversion from 'long' to 'unsigned int', signed/unsigned mismatch 1>C:\CraftRoot\labplot\liborigin\OriginFile.cpp(61): warning C4365: 'initializing': conversion from 'long' to 'unsigned int', signed/unsigned mismatch 1>C:\CraftRoot\labplot\liborigin\OriginFile.cpp(209): warning C4365: 'return': conversion from '__int64' to 'unsigned __int64', signed/unsigned mismatch -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387965] New: reinterpret_cast warning for ImportProjectDialog
https://bugs.kde.org/show_bug.cgi?id=387965 Bug ID: 387965 Summary: reinterpret_cast warning for ImportProjectDialog Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- I get: 1>C:\CraftRoot\labplot\src\kdefrontend\datasources\ImportProjectDialog.cpp(265): warning C4946: reinterpret_cast used between related classes: 'QAbstractItemModel' and 'AspectTreeModel' 1> C:\CraftRoot\labplot\src\backend/datasources/projects/ProjectParser.h(33): note: see declaration of 'QAbstractItemModel' 1> C:\CraftRoot\labplot\src\kdefrontend/MainWin.h(35): note: see declaration of 'AspectTreeModel' 1>C:\CraftRoot\labplot\src\kdefrontend\datasources\ImportProjectDialog.cpp(266): warning C4456: declaration of 'aspect' hides previous local declaration 1> C:\CraftRoot\labplot\src\kdefrontend\datasources\ImportProjectDialog.cpp(263): note: see declaration of 'aspect' -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 387967] New: encoding warnings for AxisDock
https://bugs.kde.org/show_bug.cgi?id=387967 Bug ID: 387967 Summary: encoding warnings for AxisDock Product: LabPlot2 Version: latest Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: uwesto...@web.de Target Milestone: --- Created attachment 109413 --> https://bugs.kde.org/attachment.cgi?id=109413&action=edit patch for the Unicode issue I get: 2>C:\CraftRoot\labplot\src\kdefrontend\dockwidgets\AxisDock.cpp(333): warning C4566: character represented by universal-character-name '\u03C0' cannot be represented in the current code page (1252) and 1>C:\CraftRoot\labplot\src\kdefrontend\dockwidgets\AxisDock.cpp(361): warning C4127: conditional expression is constant 1>C:\CraftRoot\labplot\src\kdefrontend\dockwidgets\AxisDock.cpp(881): warning C4127: conditional expression is constant 1>C:\CraftRoot\labplot\src\kdefrontend\dockwidgets\AxisDock.cpp(1023): warning C4127: conditional expression is constant Attached is a patch for the first issue. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 386800] Custom fitting often fails
https://bugs.kde.org/show_bug.cgi?id=386800 Uwe Stöhr changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|UNCONFIRMED --- Comment #8 from Uwe Stöhr --- > I uploaded a new package The bug persists for me, with your build and also with mine. Attached is my test file. The situation is now worse: The recalculate button is always disabled as you can see in my test file. In order to get a fit I have to create a new fit plot. -> major regression -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 386800] Custom fitting often fails
https://bugs.kde.org/show_bug.cgi?id=386800 --- Comment #9 from Uwe Stöhr --- Created attachment 109437 --> https://bugs.kde.org/attachment.cgi?id=109437&action=edit lml testfile test project showing the bug -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 386800] Custom fitting often fails
https://bugs.kde.org/show_bug.cgi?id=386800 --- Comment #10 from Uwe Stöhr --- Created attachment 109438 --> https://bugs.kde.org/attachment.cgi?id=109438&action=edit another test file with this test file the Recalculate button is always disabled -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388183] New: Windows installer is not HiDPI ready
https://bugs.kde.org/show_bug.cgi?id=388183 Bug ID: 388183 Summary: Windows installer is not HiDPI ready Product: digikam Version: 5.7.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: uwesto...@web.de Target Milestone: --- The Win installer of digiKam 5.7 looks blurred on HiDPI screens. The reason is that it uses the old NSIS 2.5. To fix this bug, simply upgrade to NSIS 3.x and use the new command ManifestDPIAware: http://nsis.sourceforge.net/Reference/ManifestDPIAware p.s. NSIS 3.x comes with full Unicode support. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388184] New: wrong folder to store user settings under Windows
https://bugs.kde.org/show_bug.cgi?id=388184 Bug ID: 388184 Summary: wrong folder to store user settings under Windows Product: digikam Version: 5.7.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: uwesto...@web.de Target Milestone: --- digiKam uses the folder C:\Users\\AppData\Local\digikam to store the suer settings. This is not wrong but is annoying if you login on another PC in your network. Therefore the folder to store user settings should be C:\Users\\AppData\Roaming\digikam See e.g. https://www.howtogeek.com/318177/what-is-the-appdata-folder-in-windows/ for a short explanation of the difference between the Local and the Roaming folder. Most programs use therefore the Roaming folder. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388183] Windows installer is not HiDPI ready
https://bugs.kde.org/show_bug.cgi?id=388183 --- Comment #3 from Uwe Stöhr --- Many thanks for the quick fix. I am sorry that I used digiKam 5.7 to report bugs. You linked me to 5.8 but on the digiKam website still 5.7 is advertised as the latest version. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388198] New: Menu Help -> What's this is not used
https://bugs.kde.org/show_bug.cgi?id=388198 Bug ID: 388198 Summary: Menu Help -> What's this is not used Product: digikam Version: 5.8.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: uwesto...@web.de Target Milestone: --- With the menu Help->What's this? I expect to be able to click on an UI element to get info. However the only element where I get info is the image editing menu buttons. So if the what's this feature is not really used the menu entry for it should maybe be disabled to avoid confusion. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388199] New: no context menu to copy coordinates from map
https://bugs.kde.org/show_bug.cgi?id=388199 Bug ID: 388199 Summary: no context menu to copy coordinates from map Product: digikam Version: 5.8.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Geolocation Assignee: digikam-bugs-n...@kde.org Reporter: uwesto...@web.de Target Milestone: --- I want to add coordinates to an image. I read the docs and in sec. 5.1.2 "Edit Coordinates" it writes: "Eventually you click with the right mouse button at the desired position and choose Copy Coordinates." The bug is that I don't get a context menu. I played around but cannot find a way to copy the coordinates. The kind of map (marble or OSM) doesn't matter. How can I get coordinated from the map? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388199] no context menu to copy coordinates from map
https://bugs.kde.org/show_bug.cgi?id=388199 --- Comment #2 from Uwe Stöhr --- > Therefore, this section must be removed in the manual. Please not. I mean that is the feature why I installed digiKam! I mean I want a program to tag the location of my holiday images. Currently I do this: 1. go to the location in OSM: https://www.openstreetmap.org/search?query=bilbao#map=18/43.26633/-2.92743 2. copy "-2.92743" to the clipboard 3. paste this to the longitude field of the geolocation editor 4. copy "43.26633" to the clipboard 5. paste this to the latitude field 6. press apply So why can't digiKam offer this?: 1. go to the desired location in the geolocation editor 2. right-click onto it in the map 3. a context menu pops up "use this location for the selected images" 4. one selects this menu 5. one presses apply to accept the change This is also possible for Google maps, because the URL contains the coordinates as well: https://www.google.de/maps/place/Bilbao,+Bizkaia,+Spanien/@43.2662736,-2.9292067,440m -- You are receiving this mail because: You are watching all bug changes.
