BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

Monthly Bugs (May 2006)

This is the continuation of the April 2006 monthly bug thread.

Rules:

  1. Each post here should only contain a brief description of a bug, together with a link to the thread where it is being discussed.
  2. One post/bug!
  3. One bug/post!
  4. No discussion of bugs. All discussions of a bug must take place in the original linked thread.
  5. Frogs not allowed to eat bugs.
  6. Please don't feed the resident frog.


LabVIEW, C'est LabVIEW

Message 1 of 17
(8,397 Views)
Bug on Open Document on Disk.vi. It fails on some filetypes that use %L as placeholder in the registry. Checked for LV7.1.1


LabVIEW, C'est LabVIEW

Message 2 of 17
(8,375 Views)
The LabVIEW 8.0 intensity graph draws everything in white if the upper marker exceeds the valid range for the datatype (e.g. 256 for U8).
 
Same VI works (and looks) fine in LabVIEW 7.0 and 7.1.
 
See this thread for details.
Message 3 of 17
(8,335 Views)
Macintosh OS X installer for LV 8 and 8.0.1 is not very nice.

1. It installs libraries in /usr/local/lib. These libraries could be overwritten by other software packages. These libraries are specific to LV and should be in LabVIEW.app/Contents/Resources or the Application support folder or even a framework folder. Same with NI-488.2 installing nipalsm in /usr/sbin. That binary could be in the Application support folder.

2. Most installed VIs in vi.lib and examples have execute privelege set. They should only be read/write.

3. Most installed LLBs in vi.lib and examples have execute privelege set. They should only be read/write.

4. The whole LV hierarchy is world writable!!! Bad, bad....

LabVIEW ChampionLabVIEW Channel Wires

Message 4 of 17
(8,306 Views)
Message 6 of 17
(8,271 Views)
PDA Right justify numbers (or work around doesn't work under WM5.0)

Just like to say ... this is an awsome idea .. .a central place for bugs to be reported an listed for the users ... great idea ...

Greycat
Message 7 of 17
(8,224 Views)
Not sure if this has been reported before but here goes:
If you make an indicator that displays a filepath, you cannot make the font size smaller. If you do, the font size still stays the same.

0 Kudos
Message 8 of 17
(8,210 Views)


GHernandez a écrit: ...If you make an indicator that displays a filepath, you cannot make the font size smaller. If you do, the font size still stays the same.

GHernadez,

I can't reproduce this problem. On my PC, using LV 7.1 or 8.01, the font size in a filepath can be adjusted by hand or programmatically without difficulty. Since no bug discussion should take place in this thread, could you post an example on the main board ?

Chilly Charly    (aka CC)
Message 9 of 17
(8,203 Views)
The issue i posted above only affects the PDA version. sorry for not stating that.
0 Kudos
Message 10 of 17
(8,200 Views)