LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabView eats color maps when running other app

Color maps are deleted from an initial 168- LabView uses 121 and then the number steadily goes down from there at the rate of ~1/hr. The other app will eventually go black.
0 Kudos
Message 1 of 2
(2,229 Views)
> Color maps are deleted from an initial 168- LabView uses 121 and then
> the number steadily goes down from there at the rate of ~1/hr. The
> other app will eventually go black.

Presumably you are talking about XWindows here. I looked through the LV
code and only find XAllocColors being called at startup of LV. I have
never heard of this before, and it would be worthwhile making sure that
this is truly being done by the LV process and if so, is it being called
by a library loaded into LV.

The strategy is basically that LV allocates either 221 (216 colors in a
6x6x6 color cube + 5 additional grays), or 129 colors (125 colors in a
5x5x5 cube + 4 additional grays). If it isn't possible for LV to
allocate these colors, it will look for shared colors
that are close.
At that point, LV should use those colors until exit.

Actually I did find a place where colors are allocated, but only when an
X specific alert box is displayed. This would likely be displayed only
as a last resort when the app is about to abort.

If this is reproducable and still seems to be a LV problem, please check
with tech support.

Greg McKaskle
Message 2 of 2
(2,229 Views)