Wrong cursor symbol when hovering over tool palette

[Dasylab User]

Hello all,

I'm using LV 8.0.1 and have noticed that very occasionally, when editing a block diagram, the cursor symbol changes to a 'barred' symbol when hovering over the tool palette even though it will still allow you to select the underlying buttons.  I can't immediately see any reason why the cursor symbol should be suggesting why these functions are not allowed. When moving outside of the tool palette area, the cursor reverts to its normal state (i.e. showing the appropriate symbol).

By closing LV, restarting LV & opening the same VI (or another VI), the problem disappears.

Is this a bug?

Regards,

Paul T.

[JamesC]

Hi Paul,

What you are seeing might be a result of an incomplete Mass Compile, or not doing a mass compile after installing 8.0.1
Please can you run a mass compile on the entire LabVIEW 8.0 directory.

To do this please Open LabVIEW 8.0.1
goto Tools >> Advanced >> Mass Compile
Select the entire LabVIEW directoy "C:\Program Files\National Instruments\LabVIEW 8.0"
Choose a log file directory if you want one.
Start the mass compile.
Start the compile when you leave work as it will take quite a few hours to complete.

Regards
JamesC
NIUK and Ireland

[Dasylab User]

Hi James,

Thanks for your reply.

I can confirm that I have already run a mass compile (although I didn't have to invoke it manually, it ran automatically after installing 8.0.1). I assumed this was sufficient?

Is it necessary to run it again manually??

Regards,

Paul T.

[JamesC]

Hi Paul,

The Mass compile after installation should have been fine. However, the icon you are describing can be seen when a mass compile did not run correctly/fully. As you can still use the icon, that seems like LabVIEW is compiling the single function in the background, so you don't notice much of a difference.

I would suggest running a mass compile again as described in my previous post, but do it over a night or a weekend, so you won't impact your work, as you can still use LabVIEW at the moment.

Regards
JamesC
NIUK and Ireland

[AnalogKid2DigitalMan]

I too just noticed this situation yesterday and came across this post today. The 1st mass compile after the 8.0.1 update did not flag any problems. I did another mass compile this AM and it logged dozens of Bad VI's. Any ideas as to why? This was a clean install of LV8 (no other previous NI software installed) shortly followed by the 8.0.1 update.

I have yet to use LV to see if the symptom with the tools pallete still exists, will keep you posted.

Attached is the mass compile log.

Thanks

[JamesC]

Hi AnalogKid,

What drivers do you have installed?
Do you have any LV 8 Modules installed (PDA, RT, Vision, ...)?
If so have you applied the 8.01 updates for the modules?
If you have DAQmx 8.0 installed, have you upgraded to DAQmx 8.1? As this fixes an error with the 8.01 mass compile and lvdaq.mxx

Do you have the latest driver installed or can you get the latest drivers?
As you compile log shows errors with DMM and DAQmx and some IMAQ errors be it driver or Vision module.
The IIOA relies on VISA so upgrading that would be good.
Finally what version of the report gen toolkit do you have?

Regards
JamesC
NIUK and Ireland

[AnalogKid2DigitalMan]

Hi James:

No additional instrument drivers installed other than what LV 8.0 PDS installed under Win XP SP2.

According to MAX I have:

 Adv Signal Processing Toolkit v 7.5.0

Database Connectivity Toolkit v1.0.132

Internet Toolkit v 6.0f1

Report Gen Toolkit for MS Office v1.1.1

VI Analyzer Toolkit v1.1

I own Vision Development Module but I did not install it on the PC since it is not needed for this application.

Thanks for reminding me about DAQmx, I am still at 8.0.0f0 since this PC has no DAQ hardware, just using the serial port. I will upgrade it to 8.1 regardless.

What is IIOA?

Thanks James

AK2DM

Curious- I ran the NI Product Updates in MAX and it did not catch the DAQmx as needing an update.

[JamesC]

Hi AK2DM,

The IIOA is the Instrument IO Assistant, so the GPIB/Serial Express VI. Most of your issues seem to be related to drivers you have installed, but I'm sure some of the missing VIs in your log were Vision.

Regards
JamesC
NIUK and Ireland