LabVIEW 2022 Public Beta
Graph corruption linked to font justification settings
As has been mentioned recently here, Graph scales can be irreversibly(?) corrupted by innocent justification settings.
This has been an annoyance for decades(!) and I wonder if this has ever been entered into the bug database. At one point, it should get some priority, IMHO. Maybe in the next beta? 😄
(I have learned the hard way to never (ever!) do any font justification when a graph is selected! It's an inescapable black rabbit hole!)
As a very simple demo, have a look at the attached VI. I dare anyone to try to get the original layout back. It seems impossible!
Any "fix attempt " makes things worse!!!! (For example we might try to "center" and reset scale layout again, but nothing good happens.)
Similarly, if we right-click the second graph and do a "justify...left", the markers get corrupted. (can be fixed by reset scale layout, but should not happen in the first place!)
If this cannot be fixed using first principles, maybe all we need is an internal barrier that will block (i.e. ignore) any justification settings to graph axes.
Similar problems also happen to scales of e.g. sliders and such (And here we don't even have a reset scale layout option!).
Thanks!
@altenbach wrote:
As a very simple demo, have a look at the attached VI. I dare anyone to try to get the original layout back.
I haven't used your VI, but if I start from scratch in LV 2015 and drop an XY graph, I can fix the scale labels by:
- Right clicking the graph, Advanced>>Customize
- Click the wrench button
- Grab the label and move it to where you want
- Apply the changes
I didn't investigate to see how the scaling works exactly (other than that the label does stay at the center. I assume the position is proportional to the scale).
Thanks for testing. We should not need to use the control editor. That's not really a solution.
(Changes that are done on the front panel, should be un-doable on the front panel.)
Right clicking the graph and selecting "Advanced>Reset Scale Layout" might reset the scales too.
However, there's no way to do this from the diagram, so it really doesn't help much.
Once you start dynamically showing and hiding scales, things go sour soon as well. The only way to do this is by handling the visibility and position manually, which is quite a task...
Search LabVIEW like a graph! 
wiebe@CARYA wrote:
Once you start dynamically showing and hiding scales, things go sour soon as well. The only way to do this is by handling the visibility and position manually, which is quite a task...
Oh yeah, at one point I started replacing much of the graph functionality with custom code for signal selection. I made some decent progress but then never actually used it on a project.
https://lavag.org/topic/21507-circular-graph-graphs-with-circular-buffer-demo/
wiebe@CARYA wrote:
Right clicking the graph and selecting "Advanced>Reset Scale Layout" might reset the scales too..
Yes, that's step #2 in my first picture and activating it will move the axis labels irreversibly to the edge. (if there were justification setting changes).
(undo works but once you forget to immediately undo things, e.g. if you notice the corruption only in the next edit session, starting from scratch seems to be the only option).
@altenbach wrote:
wiebe@CARYA wrote:
Right clicking the graph and selecting "Advanced>Reset Scale Layout" might reset the scales too..
Yes, that's step #2 in my first picture and activating it will move the axis labels irreversibly to the edge. (if there were justification setting changes).
Ah, the small letters 😎.
@Hooovahh wrote:
wiebe@CARYA wrote:
Once you start dynamically showing and hiding scales, things go sour soon as well. The only way to do this is by handling the visibility and position manually, which is quite a task...
Oh yeah, at one point I started replacing much of the graph functionality with custom code for signal selection. I made some decent progress but then never actually used it on a project.
https://lavag.org/topic/21507-circular-graph-graphs-with-circular-buffer-demo/
I've been reusing code for that, it seems to be stable.
