Bug? Tab control breaks graph autoscale (+workaround)

I had this really annoying problem where two of my graphs did autoscale and the other two didn't... Although all the code and graph properties were exactly the same.
I finally figured it out... The graphs are in a tab control. And only the graphs that are on top get autoscaling. Labview 'forgets' to autoscale the other graphs when you show those other tabs. Even when I use a property node, I can't force the graphs to autoscale, unless they are on the showing tab.
Feels like a bug to me.... I can understand that graphs aren't updated/autoscaled when they're not shown for performance reasons... but I think the axis should then be updated/autoscaled as soon as the corresponding tab is shown. And it certainly would be nice if the axis does autoscale when I explicitely ask for it using the property node...
Now that I understood the problem, I could also make a work-around. I made a 'value changed' event for the tab control, and put the property node autoscale code in it. That way, I ask for an autoscale right after showing the new tab page. (See attached vi for example of the problem and work-around.)
The workaround works fine... but I think that this should be default built-in behaviour for graphs in tabs that have the autoscale enabled.
Attachments:
tabcontrol autoscale.vi ‏32 KB

Hi Anthony,
This is a known issue that was partially fixed in LabVIEW 8, which you appear to be using. By partially, I mean that the behavior only persists when you update the value of your graph using a property node (either Value or Value Signaling). If you update the value using a direct wire connection to the graph terminal, or using a local variable, then the problem goes away. I would recommend using either of these methods, because they will fix your issue. Also, in general a direct wire connection or a local variable will greatly improve LabVIEW's efficiency in terms of updating the front panel. The only situation where this fails is if you need to update your graphs from inside a subVI using control references.
Because that last note is a very real situation, we will notify R&D of this matter so that they can investigate this further. Thanks for bringing this to our attention.
Jarrod S.
National Instruments

Similar Messages

A possible bug, Tab control in subpanel

Hi,
I think when a Tab control is used in a subpanel, it happens something faulty if you try to use right and left "tab locations". See the attached code.
will someone check the code and say if I've made any mistake or not. I see some black boxes and distortions instead of page labels when they are sorted at the left or right side of the tab control in the subpanel.
Thanks.
Attachments:
main.llb ‏29 KB

Thank you for sharing your experience. It works at my surprise!
unfortunately, in my application I'm using FP Origin property so that a part of tab control is under subpanel borders. therefore this idea won't solve my problem!
never mind. I'll think of another FP objects distribution, but I didn't expect such a simple disturbing issue
Goodluck.

Cursor Legend Tab Control BUG

Attached is a VI illustrating a bug with the Cursor Legend when graphs are in tab controls. If you enter in a number in the "Cursor X position to move to", then switch pages on the tab control, you'll notice the cursor has moved to the appropriate place, BUT the cursor legend has not changed to reflect that. Once you manually move it, it updates.
In short, if the cursor position changes programmatically, the cursor legend will update ONLY IF THE XY GRAPH IS VISIBLE, even though the cursor position DOES change.
I hope someone from NI will see this post and add it to the bug list (if not already there??). If anyone knows a work around, that would be appreciated also.
Michael
Using LV 8.2
Attachments:
CursorLegendTabControlBUG.vi ‏27 KB

Good idea. It doesn't work exactlly, but gave me the idea for how to work around. It appears even if you have a tab value change event doing the same thing the Cursor X Position numeric indicator value change event, the cursor legend X value will not change. You can even try entering the same value in the indicator and pressing return after switching tabs, the cursor legend will not update. It thinks for some reason it is on the correct index. I made a Tab Value change event that first moves the cursor to the next index, then moves the cursor back to the correct index. Ugly but works. Hopefully in the next ver of LV they will have fixed a lot of these cursor bugs; there is definitely some work to be done (i.e. fixing cursor X position for XY graphs, an extremelly annoying bug)
Michael
Message Edited by miguelc on 02-23-2007 03:49 PM
Message Edited by miguelc on 02-23-2007 03:50 PM
Attachments:
CursorLegendTabControlBUG_wrkaround.vi ‏34 KB

Graph range problem with tab control

Hello.
I am using LabVIEW 8.2.1
I have five XY-graphs in a tab control, with five tabs. One graph in each tab. When running, theese graphs is constantly written to, but the user is only allowed to watch one at a time.
The program also contain a maximum&minimum chart, containg the maximum and minimum value for every plot in the viewable part of the graphs. The user can zoom in on a graph, and then watch the max&min values in this picture. The values are calculated by taking the range to each graph, and use theese ranges to cut out the viewable part from the input data to the graphs.
The problem is, that the program only see the last viewed range. If I view a graph in a tab, the max&min values for this graph is correct, but the four other graphs dont get the correct values. The graphs data is written correctly. It seems like the ranges from the "hidden" graphs dont get updated when not viewed. Does anybody know how to fix this problem?
I have uploaded an example to this problem. See how the range just freezes on the not viewed graph, even the two graphs is exactly the same.
Thanks
Fredrik, Norway
Message Edited by Kalman on 06-19-2008 01:58 AM
Attachments:
graph_range_problem2.vi ‏24 KB

Frederik,
the reason for your issue is autoscaling. If the graph is not drawn, autoscaling will not take place, so you will not get any correct values, you will get the last autoscale-values.
The behaviour therefore is "works as intended" since it reduces CPU usage.
So the best way to work around is something like seen in the attached VI: you should compute the scaling for each graph on your own and use this to update the scales as well as the indicators (which i left out in my VI).
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Attachments:
Scaling.vi ‏25 KB

Obscured Labels - Graphs and tab controls

In LV 2012 new options (Preferences or Options on the Mac) allow placing labels on new controls and indicators in various positions. I have noticed that for graphs and tab controls some of the options result in obscured labels. See the image below.
The preferences are set as shown:
When a graph is dropped, the label is superimposed on the plot legend display.
For a tab control everything is OK until enough tabs are added to create a second row. Those tabs are behind the label. I can understand some reluctance to move a label automatically after it has been created (in the tab case), but I think it would be better moved up than obscured. Perhaps if the programmmer had repositioned the label before the tabs were added, then it should not move automatically.
Is this a bug?
Lynn

Hi Lynn,
I've played around with these settings and I get the same results. It seems with the tab control that the new row of labels is pushed to the top by default, and the label will be obscured unless it has been placed to the bottom or side of the control. After looking into things further it seems that this is the expected behavior rather than a bug. You're welcome to post your idea to the Idea Exchange as a feature request, it seems like that might be a better way to handle the label positioning in the future.
Matt Lee
National Instruments
Applications Engineer

Possible bug with Tab Control and Context Help?

I created Description and Tip text for each Tab of a tab control I am using on my front panel. I have a subVI that is called by selecting a menu item from my main front panel. The subVI's front panel also has a menu system and a Tab Control. I have Description and Tip text written for each of the tabs on the subVI's front panel.
When I enable context help from the menu of my main VI, the proper help text shows up for the tabs on the main vi and, when I bring up the subVI's front panel, for its tabs as well.
So far so good...
Now I builld the application and run it as an executable. For ALL of my panel tab descriptions, I get the tab's label in bold text, but no description (just a blank area).
Is this a bug in LabVIEW?
Kevin

wired wrote:
I'm still seeing this behavior in LV8.2.1. Does anyone know if/when it was fixed? Also, my tip strips show up in the corner of the monitor when I mouse over a tab (in both the executable and the development version).
I see it still even in 8.5.
The Help part of the bug is still NOT fixeed by NI.
But I dont get the tool tip appearing in the corner of the monitor, it is showing up as usual.
- Partha
LabVIEW - Wires that catch bugs!

Text Tool on Tab Control Bug?

I'm trying to create some free labels on a tab control with the text tool and I've found the postion of the text insertion point is off. When I click anywhere on the tab the text appears a few inches above the point that I clicked on. The tool is working fine off the tabs and when I go to select the previously written text with it that works too. I've noticed the insertion point jumps around and is often in a new place when I open a new VI and drop a tab control down. I have free text on tabs I created last week so I know it wasn't doing it then. Has anyone else seen this behaviour?
Using LabVIEW: 7.1.1, 8.5.1 & 2013
Solved!
Go to Solution.

Hi NIquist,
Your problem has been discussed in another thread and considered as Bug in LabVIEW 8.6 and reported as CAR. Have a nice day!
Sincerely,
Krisna Wisnu
Sincerely,
Krisna Wisnu

When I resize the font for the Page Labels on the tab control in LabVIEW 7, the Increment/Decrement size gets messed up. Is there a solution to this problem or is this a bug?

I have noticed in LabVIEW 7.0 and 7.1 that when the text in the page labels display is enlarged, that the arrows enlarge but the top arrow enlarges more then the small arrow but then when you decrease the text size, the arrows stay remain large. This is not a problem in 6.1 because the arrows aren't available. Is there a work around for this bug or do I have to use small text for these page label arrows to look right?

I must admit that I've never used the page labels display and it does look like a bug. You can fix it however. Select the tab control and choose Advanced>Customize. In the control editor, select the page label control and do the same thing. You should be in the control editor for the numeric control and then you can go to edit mode and enlarge the decrement arrow to make it the same size as the increment.

Tab Control Typedef Bug (LV 2014)

If you have a typedef'd tab control, and you rearrange the pages in the typedef, then apply the changes, on the instances of the typedef, only the labels will be rearranged, not the contents of the pages. Each control on the tab control will be on the same ordinal page as before.

Paul,
If you can post a simple example VI that shows this behavior I would be glad to take a look at to see what is going on and if this is a bug. If it is a bug I will make a Corrective Action Request (CAR) so that this can be fixed in future iterations of LabVIEW. The post I made earlier, that suggested this may not be a bug, referenced the help documentation for the Rearrange Pages Method. This document is linked below and states that the method is not available for Strict Type Definitions.
http://zone.ni.com/reference/en-XX/help/371361K-01/lvscript/tabcontrol_rearrange_pages/
This is the LabVIEW 2013 Help documentation and as I noted in my previous post, the remark on whether or not it is available with strict type definitions in LabVIEW 2014 help was absent. If you would be willing to post a VI that demonstrates this behavior I can try this on my computer using multiple versions of LabVIEW and ask a few colleagues to determine whether this is a bug.
Matt J
Professional Googler and Kudo Addict
National Instruments

Tab control bug?

I have a problem with tab control which has been bugging me for a long time and i can't seem to solve it.
I have a tab control with 4 pages, A, B, C and D. All these pages are invisible at the beginning. Once the user selects the page from the custom run-time menu, the appropriate page then showns up (PageVis=True). Now, when i try a few more times switching between different pages, some pages showns up together with the intended page. Once i click the correct page's tab, the others disappear. Now this is a problem because when a user is using page A, i do not want he/she to be able to access other pages.
Can someone help me before i kill someone? Thanks.
Attachments:
tab.JPG ‏27 KB

The order of the property nodes is not defined because you have no dataflow between. Execution order is not defined by where a function is on the block diagram (left, right, top bottom), but how data is connected. You have no connections between the properties so they execute in parallel and you have no way of knowing which one will actually execute first. The simplest way to enforce dataflow is with the error in/error out connections. That is shown below. also shown is one way to select the active page. I used a local variable but if you make the tab control an indicator instead of the default control, just wire a value to the terminal itself.
Message Edited by Dennis Knutson on 07-26-2007 08:16 PM
Attachments:
Tab Control.PNG ‏13 KB

How do I create more tabs in my tab control, and place graphs/charts on these.

It has to be done in the program depending on a setup file.
This is due to that I have from 2 till 100 graphs/charts needed to be shown. One graph/chart on each tab.
How many tabs I need comes from the setup file.

This is not really a goo way to approach this. 100 tabs ouch. This would not only be a nightmare to code and keep up to date but I think it
could be done. Here is an examlpe of how to do it in LV 8 and a file saved for previous into 7.1 it seams to me it was easier to do in lv 7 but I cannot be sure since I no longer have 7.0 or 7.1 on this machine.
Joe.
"NOTHING IS EVER EASY"
Attachments:
Tab control.vi ‏21 KB
Tab control1.vi ‏39 KB

LabView crash when intensity graph is in P6 of tab control

Any available fixes for LabView crash when intensity graph is put on page 6 of tab control and right-clicked??

Michael,
This has been fixed in LabVIEW 6.1.
Regards,
Cyril Bouton
Applications Engineer
National Instruments
Cyril Bouton
Active LabVIEW Developper

Bug in Tab Control when inserted into SubPanel

Just would like to report about pretty old bug, which is still present in latest LabVIEW 2013 SP1 13.0.1f1.
I would like to insert SubVI with Tab Control into SubPanel, something like this:
When SubVI executed, then I will set it to Page 2:
Now what I've got in my SubPanel:
Page 2 is active, but selector is not actualized - still show me active Page 1. Fully inconsistent.
Not sure if it was reported already or not, but needs to be fixed from my point of view.
Attachments:
main.llb ‏25 KB

mikeporter wrote:
But yet another problem with tab controls...
Seriously though, if you are already using a subpanel why complicate matters with a tab control?
Dynamically swap VIs in and out of the subpanels to present the same user experience as there was with the tabs.
You're right - there are many ways to workaround about this bug. For example, if I will use Property Node instead of terminal or local variable, then it will working properly.
This contstruction with tab control in subpanel used in my settings dialog. I have modular plugin architecture, and some plugins may have settings, so they organised in the same way as LabVIEW Options dialog - listbox with installed plugins and subpanel, where according subvi from plugin is inserted. Mostly all plugins fit into my dialog (which is not resizible at this moment), but some modules have lot of settings - then they splitted into groups and the tab control is used (NI does this with vertical scrollbar, which is also not perfect).
When user made changes in settings, then last opened page is saved - when this dialog opened next time, then user should see last page - this is why I need to set page programmatically.
Really, I don't like to change whole architecture for workarounding bug in LabVIEW just for few modules. At this moment I using property node and it works for me.

Need a multi-level control break report displaying a cross-tab for each ...

I need a multi-level control break report that displays a cross-tab report for each
detail and subtotal. The individual cross-tabs are no problem. There are two issues:
1) How to get many cross-tabs (thousands) to appear in one report.
2) How to provide cross-tabs in-line on the multi-level subtotal lines.
Here is a concrete example.
Suppose the data base contains this table:
road (
id_number number, -- this is an artificial PK
city varchar2,
county varchar2,
state varchar2,
length number,
owner varchar2, -- roads may be owned by cities, counties, states, and others
surface_type varchar2 -- the surface type may be gravel, asphalt, concrete, and others
The table is populated with several million records that include every
length of road in a US city.
It is OK to suppose that all the attributes in all the records are not null.
Without the PK, there would be millions of duplicates,
which should all contribute to the summed lengths.
The report I need is like a control break report with a detail line for each
city together with subtotals for each county and state and
a grand total for the US at the end.
However, each detail and total line needs to be a cross-tab report
summing the length over the city, county, state or US
(whichever is called for at that location)
for each combination of owner and surface_type.
so the report would have the following structure:
a city cross-tab for the first city in county 1/state 1
a city cross tab for the last city in county 1/state 1
a cross-tab for count 1
a city cross tab for the first city in county 2/state 1
a city cross tab for the last city in county 2/state 1
a cross tab for state 1
a cross-tab for the US
Any suggestions will be appreciated.
This problem comes up because my client's legacy system,
which is being replaced,
already has such a report (in COBOL).
Thanks!!!
Steve
PS, I know one ugly way to do it. Namely, make a variable for each
possible combination of owner and surface. Then code an ordinary control
break report. However, I am looking for something better.

Hi Jenna_Fire,
According to your description, you have a matrix contains total for each group on each level. Now your requirement is, when you click on any number (data field or total), it will go to the detail report which returns all the detail information of the people
within the group scope. For example, if you click on the total of Active users in United States, it will return the detail information of Active users in New York and Texas. Right?
In this scenario, we should set the parameter (@Country, @State, @City) allow multiple values in both main and detail report. And in Default Value (@Country, @State, @City), query out all distinct values. In the textbox which contains
those total values, when set use these parameters to run the report, we only need to pass the parameters of parent groups. For example, if we click on the total of Active users in New York, we only need to pass Country, State, Status to detail report, and
in the detail report, the City parameter will use all distinct values (Default Values) because we don't pass the City parameter. We have tested this case with sample data in our local environment. Here are steps and screenshots for your reference:
1. Create parameter Country, State, City and Status in both main report and detail report. Set both Available Value and Default Value get values from query (Create a dataset for each parameter, use "select distinct [column] from [table]" as query). Set allow
multiple values for parameter Country, State and City in both reports.
2. In corresponding textbox, pass appropriate parameters in go to report Action.
4. Filter data in detail report (in where clause or using filters).
5. Save and preview. It looks like below:
Reference:
Using Parameters to Connect to Other Reports
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Bug Report (Tab Control)

A way to crash LabVIEW:
1. Open a new VI
2. Create a Tab Control on the front panel.
3. Select the second tab "Page 2".
4. With the text tool, clear the tab label completely.
5. Right-click the now empty tab, select "Add Page After."
Verified with LabVIEW 7.1 under Windows, with an old 7b43 beta under MacOS X and with 6.0 under Solaris. The Unix log is attached.
Harald Grundner
Attachments:
tabcrash.txt ‏2 KB

Hi
I tested it, and it crashes in 6.0, 6.1, 7.0 and 7.1 (all the versions I
tested it on)...
Regards,
Wiebe.
"Harald Grundner" wrote in message
news:[email protected]..
> A way to crash LabVIEW:
>
> 1. Open a new VI
> 2. Create a Tab Control on the front panel.
> 3. Select the second tab "Page 2".
> 4. With the text tool, clear the tab label completely.
> 5. Right-click the now empty tab, select "Add Page After."
>
> Verified with LabVIEW 7.1 under Windows, with an old 7b43 beta under
> MacOS X and with 6.0 under Solaris. The Unix log is attached.
>
> Harald Grundner

Bug? Tab control breaks graph autoscale (+workarou​nd)

Similar Messages

Maybe you are looking for

Bug? Tab control breaks graph autoscale (+workaround)