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

Similar Messages

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.

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!

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

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

Bug Report : Upgraded to Firefox v10. Holding CTRL+ [F4] too long after all tabs are closed causes error. "Exc in ev handl: TypeError: this.oPlg.onTabClosed is not a function"

Bug Report :
Upgraded to Firefox v10. Holding CTRL+ [F4] too long after all tabs are closed causes error.
"Exc in ev handl: TypeError: this.oPlg.onTabClosed is not a function"

What extensions do you have? (Go to Firefox > Customize > Add-ons to see or Help > Troubleshooting info for a copy-pasteable list)

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

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

Report Tab in Mitigation Control

Dear Experts,
Can anyone explain me the purpose/usage of Report Tab in Mitigration Control. I have browsed the forum but could not understand the actual need of this tab as I found different answers.
Thanks,
Raj

HI Raj,
Access Controls is used as a documental tool for Mitigating Controls, rather than a implementing tool, i.e. you apply the control against the role/user, but the actual application of the control is performed outside of Access Control. This may be realized by running a custom SAP report to monitor the usage of the risky functions within the ECC system etc.
Access Control allows you to document such reports against the Mitigation Control, so this is the purpose of the tab. Given that GRC 10.0 integrates AC and PC, Mitigating Controls is master data that is shared amongst the different GRC modules, so I get the feeling Process Controls might utilize the "Report" data and check if the reports are being monitored by the control monitor/s at the scheduled frequency etc.

Report tab in mitigating control - RAR 5.3

While creating mitigating control there are 3 tabs - Associated risks / Monitors / Reports. What is the use of reports tab ?
The control is working even with populating the report tab.

If you have a report that you want mitigation monitors to run in order to perform the control activities you can put it in there.
The alert functionality will then allow you to report on monitors that did not run that report in the specified period.
Frank.

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.

Reproducible Sloooooow Backup Bug (how do I submit a bug report?)

I've been having incredibly slow backup problems with my iPad. My wife was foolish enough to leave her iPad here today, so I'm doing some experiments, and I think I've identified the problem.
Her system had 2.5 gigs of stuff on it, and took less than 2 minutes to backup in iTunes on my desktop computer. I added ComicZeal, and copied 2 gigs of comics (261 issues) onto the machine. It took 90 minutes to back up.
Delete the comics, less than a minute to backup.
Add two gigs of music, less than 5 minutes to back up.
Add back two gigs of Comic Books in ComicZeal, and I gave up on the backup at the 75 minute mark (about 2/3 through).
So how do I file an official bug report?

Yep, this is consistent with what I'm seeing with cloudreader (and other pdf readers the in this case the files were pdfs but also coincidentally comic files as above). After an excruciating first back up the first time I synced, subsequent backups were reasonable (5-10 mins).. until I added a large number of pdfs to various installed pdf readers via itunes app sync tab (I was testing the different apps to see how they handled large pdfs). Adding the files to itunes took minutes but the subsequent backup the next time took hours - I've been following the hidden backup folder and the new back up files are similar in size to the pdfs. Using the time stamps on the backup files, one 100meg file took about 20 minutes to back up. I've tried both the original ipad cable and my iphone cable but little difference in speed. By contrast, my 8gb iphone backs up in 5 minutes is full but does not have any pdfs stored on it.
So Apple either needs to speed up / fix the sync or at least give the user more control over what is and isnt backed up.
Scott

Bug Report: The keyboard focus doesn't automatical...

Bug Report: When a conversation window opens, the focus doesn't automatically land in the chat entry text field.
Since the new interface for Skype was introduced officially in Skype 7.0, there is a bug with the system/keyboard focus for a new conversation window. When Skype is in "Split Window View" and each new conversation automatically pops up in a separate window, the system/keyboard focus doesn't land in the chat entry edit field. Instead, the user has to press Shift+TAB a couple of times, to move it there and reply to the chat message received. This especially problematic for screen reader users, who rely on keyboard navigation. This mainly occurs when a new conversation is started with an incoming message, but it sometimes occurs when moving the focus out of that conversation window and later back in it again (while it is still opened).
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Tell someone to send you a chat message. When the message arrives, Move the system focus to the conversation window in question, preferably with Alt+TAB. The system/keyboard will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should by default, but in some unknown place in the window.
7. Move the system/keyboard focus in the chat entry edit field and keep it there.
8. Switch to another window, preferably from another application.
9. With Alt+TAB, switch back to the window of the opened Skype conversation. There is a chance that the system/keyboard focus will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should do by default, but again in some unknown place in the conversation window. But that is harder to reproduce.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Bug Report (Tab Control)

Similar Messages

Maybe you are looking for