I just came to realize that the axis values do not align with the data sets. I'll send some screenshots where all ranges have been selected to 'auto'. In those screenshots the axis should be placed at 0.218, but the screenshots give a different picture ... When I adjust the ranges manually the axis values do things that I don't really understand. For me as a stupid user this is all incomprehensible. bye Michi
Created attachment 119944 [details] exmple 1
Created attachment 119945 [details] example 2
Without having looked into the settings in your project yet, I'd assume this is because of the rounding for the axis labels. In the properties dock widget for the axis, navigate to the tab "Labels", uncheck "Auto" for the precision and specify the precision you need.
Created attachment 120030 [details] it's not about precision the precision has been manually adjusted according to advice, but it does not touch the core of the problem. In this screenshot one can see one and the same data set. The range of the y-axis of the scatter plot has been manually adjusted, which I assume should have consequences on how the data set(s) are displayed, but that doesn't happen. Instead the y-axis shows labels which I can't make any sense of; setting the range from 1.5 to 1.7 removes all labels, for instance. Btw. the x-axis should intersect at 1.65
(In reply to Michi from comment #4) > Created attachment 120030 [details] > it's not about precision > > the precision has been manually adjusted according to advice, but it does > not touch the core of the problem. > In this screenshot one can see one and the same data set. The range of the > y-axis of the scatter plot has been manually adjusted, which I assume should > have consequences on how the data set(s) are displayed, but that doesn't > happen. Instead the y-axis shows labels which I can't make any sense of; > setting the range from 1.5 to 1.7 removes all labels, for instance. > Btw. the x-axis should intersect at 1.65 Sorry, I'm still not quite sure I understand your problem correctly. Can you please attache your project and I'll check quickly the settings you did? Disappearing of labels is another problem which have sometimes. This needs to be fixed urgently.
Can you please attach your project file?
(In reply to Alexander Semke from comment #6) > Can you please attach your project file? Hi Alex, sorry, but I have moved on and I'm currently not using labplot anymore, it was too frustrating. I couldn't trust the diagrams anymore. bye Michi
well, I asked you to provide the project file almost one year ago, soon after you reported this issue. We could have fixed this problem fast and avoid any kind of frustration. This is an open-source project developed by people in their spare time and we also need user's feedback to improve the software. Not providing the information the developer has kindly asked for and report after this frustration is not the feedback that helps us.
(In reply to Alexander Semke from comment #8) > well, I asked you to provide the project file almost one year ago, soon > after you reported this issue. We could have fixed this problem fast and > avoid any kind of frustration. This is an open-source project developed by > people in their spare time and we also need user's feedback to improve the > software. Not providing the information the developer has kindly asked for > and report after this frustration is not the feedback that helps us. Hi Alex, alright, I did not provide the project file - my bad. I think there were some company specific information in it and I wanted to remove that first, and then I forgot ... What added to my decision though was Bug 403304 which is more of a biggy, for me as a user, and as it seems for you as a developer as well. So, my appologies if I was hurting your feelings, it was definitely not my intention. I really appreciate what you are doing. bye Michi
(In reply to Michi from comment #9) > What added to my decision though was Bug 403304 which is more of a biggy, > for me as a user, and as it seems for you as a developer as well. Bug 403304 is very important, yes. But unfortunately the effort for this is also somewhat big for us so that it won't make into 2.8 anymore. We're finalizing 2.8 now and hope to release soon. After this we'll start working on 2.9 and 403304 will be addressed. In case you still have the problematic data or can reproduce the issue originally reported in this bug report with some random or randomized data, I'm still very interested to understand and to fix it. Thanks.