BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

Weekly Bugs

Since Ben seems to be short on time (my advice - read the breakpoint and feedback threads, and if you have time, the rest) he wants a reader's digest version of the forums.
So, here's the first bug to make it (not including LIST ones [just kidding, CC, you can relax]):
Something to do with a combo box and hex display. To be honest, I didn't really read it.

___________________
Try to take over the world!
Message 1 of 26
(9,023 Views)
Ben, here's another one for you.
This is my favorite (if that's the right word) since it was extremely annoying and very hard to find (and it happened to me).

___________________
Try to take over the world!
Message 2 of 26
(8,998 Views)
One more graph bug, this time in the 3D library .

Where are these stars ?

CC
Chilly Charly    (aka CC)
Message 3 of 26
(8,968 Views)
I haven't had a chance to check this one, but he says it's a bug\unexplained behavior (and it's picture control, Ben).

___________________
Try to take over the world!
Message 4 of 26
(8,923 Views)
I don't like the way that the Front panel option "End text entry with enter key" appliesinterferes when trying to enter text in a formula node on the diagram.

See This thread for details.
Message 5 of 26
(8,883 Views)
Typedef label\caption don't dim when disabled.

___________________
Try to take over the world!
Message 6 of 26
(8,864 Views)
OK I think i might mave stumbled across a bug. Granted I'm only using 6.1, but maybe it's still lurking.

I was trying to use the "Scan tokens from strings" function to find a %nm% placeholder for a wavelength value. The problem is that it wasn't found. Not understanding this, but thinking it maybe had something to do with the "%" sign, I changed them to *nm* and it worked.

Seems logical enough. But then I just had to go and dig deeper. By replacing ONE of my token array with a *xx* palceholder, I suddenly started getting results. Wierd. Of course, I had to dig deeper.

Here's a VI demonstrating the problem. I've also found out that the caching behaviour is somewhat suspect.

Try the VI first with default values, then with caching forced "off" ("off" SHOULD be the default). The first and second results come from the same functionality, with the same inputs, but they are different. By forcing "no caching", the results are the same. I don't understand this, but it gets better.

Then try changing element 2 or 3 (which isn't present in the string to be searched) from a "%xx%" value to a "*xx*" value (simply change the "Array element to replace" from -1 (no action) to 2 or 3). Lo and behold, the %nm% token is found, and the forced caching has no influence any more.

I may be missing something with the "%" character, but can someone explain this to me?

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
Message 7 of 26
(8,823 Views)
The debate on Shane's bug should continue here.

___________________
Try to take over the world!
Message 8 of 26
(8,796 Views)
I'm not sure about this one. I'm not into formula nodes and I don't have LV available at the moment to check whether it's a bug.

___________________
Try to take over the world!
0 Kudos
Message 9 of 26
(8,783 Views)
Thanks to Ben for bringing this post to our attention and to all of you for documenting these bugs. We are now documenting and investigating these bugs ourselves and putting them through our internal processes. We typically do not monitor the non-product-specific forums (such as BreakPoint), so I encourage you to submit any bugs you find directly to us through either email or by phone (link). If there's a bug out there, we definitely want to know about it, and submitting them directly to us ensures that they go to the right place and are properly dealt with!

Thanks again to all of you for your hard work, and keep up the bug hunt!

Best Regards,
E. Sulzer
Applications Engineer
National Instruments
0 Kudos
Message 10 of 26
(8,766 Views)