topic Re: Monthly bugs, August 2008 in BreakPoint

Monthly bugs, August 2008

altenbach — Fri, 01 Aug 2008 07:03:42 GMT

Lets all celebrate the Swiss Independence day: August 1! 😄

This is the continuation of the July 2008 bug thread. The rules are as always:

Each post here should only contain a brief description of a bug, together with a link to the thread where it is being discussed.
One post/bug!
One bug/post!
No discussion of bugs. All discussions of a bug must take place in the original linked thread.

BugSSSS in the new 3D surface graph (LV 8.6)

chilly_charly — Sun, 03 Aug 2008 05:55:55 GMT

I just downloaded LV 8.6, as I could not wait to have a look at the new long time awaited 3D graphs primitives, said to run also on MacOS. This is a great new feature.

Of course I found a collection of new bugs (probably known already by the development team since they are pretty obvious, but who knows...)
Additionnaly, I enjoy the idea that this seems to be the first LV 8.6 bug report in this forum.

OK, here we go : (all the bugs have been found on a WindowXP machine)
1 - As shown in the attached picture, a transparent cursor plane hide the 3D surface graph (but shows the axis)
2 - As shown on the same picture, the boundaries of a cursor plane are locked to the axis values defined by the axis autoscale mode. The cursor plane appears much wider than the axis.
3 - While in "perspective" mode, when the 3D indicator size is changed the graph switches to "orthographic" mode. An access to the property window is required to return to "perspective" mode.
4 - after an access to the property window, the graph (perspective mode) in the Render window is streched to fit the window area, but returns back to a normal aspect ratio as soon as the window size is slightly changed.
5 - As shown in the second attached picture, after a slight modification of the window size, the 3D surface is chopped of during a zoom-in.
6 - When the 3D indicator size is streched, the graph is also streched. That gives the graph a poor look during rotation. In the old 3D activeX the aspect ratio of the graph was preserved.
7 - (Not a bug, but a major lack of functionnality) I could not find a way to draw a 3D surface and a line on the same graph. This is easy with the old ActiveX and is a very usefull function when you want to represent the trajectory of an object moving onto a surface.
8 - (Not a bug, but a strong inconvenience) A predefined color spectrum is lacking
9 - (Not a bug, but a minor inconvenience) No logarithmic mode for the axis scales

I better stop now since my wife is desperately asking me to pack my luggage before we leave for NIweek ! See (some of) you soon in Austin !

Message Edité par chilly charly le 08-03-2008 07:55 AM

Re: BugSSSS in the new 3D surface graph (LV 8.6)

tst — Sun, 03 Aug 2008 10:05:35 GMT

Charly's thread is here.

Fake (hopefully) coercion dots.

altenbach — Fri, 23 May 2014 14:49:28 GMT

There's an apparent bug that got started with 8.5 (8.2 and earlier are OK).

Look at the picture in this thread:

As you can see, the "number to decimal string" shows a red coercion dot.

Wiring an array to any of the integer type "number to (decimal|octal|hex) string" conversions shows a coercion dot (any array input, from I8...U64, FXP, DBL, EXT will do). The coercion dot only disappears if I wire a scalar.

The noninteger type conversions "number to (fractional, exponentional,engineering) string" never show a coercion dot. This seems like the correct behavior.

Here is a more general illustration:

Message Edited by altenbach on 08-07-2008 04:05 PM

Message Edited by Support on 11-14-2008 09:25 AM

Re: Fake (hopefully) coercion dots.

muks — Fri, 08 Aug 2008 11:27:51 GMT

Hi altenbach,
Can you repost it? please

Message Edited by muks on 08-08-2008 06:27 AM

Re: Fake (hopefully) coercion dots.

Mathan — Fri, 08 Aug 2008 12:34:59 GMT

Fake (hopefully) coercion dots

Re: Fake (hopefully) coercion dots.

muks — Fri, 08 Aug 2008 12:40:59 GMT

Thanx Mathan

So this is the image altenbach had mentioned.....

Message Edited by muks on 08-08-2008 07:40 AM

Transformation VIs return stale data if array inputs are empty.

altenbach — Tue, 12 Aug 2008 23:14:31 GMT

Most VIs from the Math...Geometry palette return stale data (+an error) if the input arrays are empty array.

Correct would be to (1) return an error and (2) empty arrays.

See:

http://forums.ni.com/ni/board/message?board.id=170&thread.id=348574&jump=true

According to some casual testing, all 6 VIs are affected.

Message Edited by altenbach on 08-12-2008 04:14 PM

Re: Monthly bugs, August 2008

Neil.Pate — Thu, 14 Aug 2008 15:01:00 GMT

Not a bug, but an inconvenience:

In LV 8.5.1 if you right click on a compound arithmetic node (which lives in the Boolean palette) and choose replace it has a shortcut to the Numeric Palette as opposed to the Boolean Palette.

(by far the majority of the time I use compound arithmetic it is for multiple input AND/OR).

Re: Monthly bugs, August 2008

PhillipBrooks — Mon, 18 Aug 2008 14:15:02 GMT

LabVIEW 8.6

"LabVIEW crashes immediately when you try to use a subroutine within a for loop."

This was reported to R&D (# 123264) for further investigation.

Reported on the LAVA 8.6 Buglist forum: http://forums.lavag.org/Very-ugly-bug-in-LV-86-t11706.html

Dynamic events cannot be registered under some conditions.

altenbach — Mon, 18 Aug 2008 16:05:54 GMT

IT seems dynamic event registration fails if the respective front panel is not open. Since a corresponding error is generated, this might be an expected limitations.

Still, I cannot find this documented anywhere, so at a minimum it is a documentation bug.

This limitation should be removed if possible or at least be documented in the help for "Register For Events".

See this discussion for an example and more details.