The results of the "combat" use of the program. #42
Comments
|
Well, thank you for the points. Some of your points will be addressed in next release. Backend
Frontend
GUI inconvenience
Wishes
At the moment my first priority is to maintain and improve up on 2D graphing glitches. Along with that the property editor needs a back-end change which is the most critical one. Sadly open source projects have few contributors. So at the moment we don't have a team to work on this. You are welcome to join if you have the time. Thanks for the feedback. |
|
This close to simple sinus. You should find 4 peaks here:
gauss.csv The result should be similar to this, this is also a substance but with slightly different parameters.
Hm. I meant that there is no table with the results of the approximation, and I have to take them from the log. And I do not want to take them from the log, I want a separate dryness. You need a separate window where it would be displayed, both the points themselves and the coefficients. Desired view of the project exploer. |
|
Regarding the xml format. It looks like you are really right, he leaves no alternatives. But I still do not agree that an ordinary person cannot read a file, a project, simply with a text or spreadsheet editor. That's why I wrote about the archive containing csv + ini. Some data analysis programs actually do this, though without an archive, just a text file. |
|
thank you for the inputs. I will have a look at it soon.. |
I am writing this because I want to draw attention to the really important points, software is still written not only in order to write it.
Backend
A serious glitch with approximation: going out of range leads to an incorrect result.
Crashes are observed when trying to edit the approximation result.
Gaussian peak approximation leaves much to be desired, and really works only in simple cases.
Charts in polar coordinates never appeared in the program. You can still be the first among free origin clones)
Frontend
The points of the approximation curve are not displayed in a separate table, and if they are, then it is difficult to understand that this is what you need.
There is no separate table with the results of the approximation itself, such as the correlation coefficient, you have to get it from the log.
Hotkeys don't always work as expected, but that's the lesser of the evils. I mostly miss alt+C (was in the original qtiplot) for a new column, and enter has to be pressed twice to move to the next line when manually typing.
GUI inconvenience
The application does not remember the layout of widgets.
The settings window in the old version was better, it's actually generally funny here. Everyone moves away from this view in their designs, you returned to it)
The table settings window generally justified itself, but it is much more difficult to work with the same for charts. For good, both need a redesign, the main complaint is too small elements. It is possible to make duplicate layers, which should not be.
No syntax highlighting in Approximation Wizard, parameters are not added automatically.
Sometimes the width of the last column is naughty, stretching to the end. In my opinion, it should be wider than some x and not wider than necessary.
Wishes
Tabs in tables as in origin pro.
Tabbed mode as in kde's labplot.
More human readable data format instead of xml. I would prefer to see there an ordinary archive with an internal structure, settings files and csv and other data files. Yes, it will weigh a lot, but not globally, for that people without a program will be able to figure it out.
A slight redesign of the project browser to better fit vertically would also help.
These are the results of the real application of the program in scientific work and education, and this list is more important than porting to cmake and qt6.
In my opinion, the tester needs the team.
It is worth noting that at the moment you have done the best among the open clones of Origin Pro.
The text was updated successfully, but these errors were encountered: