context help

[saverio.mercurio]

Anybody have problems with the context help window not updating itself in LabVIEW 6.1? I have the window open and whenever I move to a different object in the block diagram the context help does not update to reflect the object that is currently underneath the cursor. The context help works just about everywhere else, though.

[Jim_Kring]

I have found that clicking on the item to select it (and switching back and forth between objects) will wake up the context help.

Good luck,

-Jim

[saverio.mercurio]

Yeah, I tried that at first, but I found that it rarely worked. Thanks for the input.

-Saverio

[wiebe@CARYA]

Hi,

Does it work when the VI is not running?

If it only happens when the VI is running, it could be a proccessor problem.
Check the task manager, if the processor usage is 100%, the help might not
get the time needed to update.

Regards,

Wiebe.


"saverio.mercurio" wrote in message
news:50650000000800000067720000-1042324653000@exchange.ni.com...
> Anybody have problems with the context help window not updating itself
> in LabVIEW 6.1? I have the window open and whenever I move to a
> different object in the block diagram the context help does not update
> to reflect the object that is currently underneath the cursor. The
> context help works just about everywhere else, though.

[Greg_McKaskle2]

> Anybody have problems with the context help window not updating itself
> in LabVIEW 6.1? I have the window open and whenever I move to a

Be sure to check that the help window isn't locked. The lock icon and
Ctl-L toggle whether the help window updates or keeps the current info.

Greg McKaskle

[saverio.mercurio]

It's not. That's one of the first things I checked. Neglected to mention it in my post.

I have found out something interesting, though, about this aberrant behavior. Even though the context help window does not update when I move to a different object, it does update if the object I move to is a construct like a case structure. If I then move to a different object, like an Add function, it still stays showing the case structure help.

[saverio.mercurio]

This is while I'm editing the diagram.

In case the follow-up question is asked: I have a pretty good machine. 2GHz P4, 256MB RAM, with Windows XP. It's not smoking, but it's quite peppy.

[Ed Ward]

I have the same problem when I have my mp3 player running concurrently
with LV. The only thing that cures it is to shut down (not merely
pause) the player. Try closing out everything but LV and see if the
problem goes away.

Ed

[wiebe@CARYA]

The processor can still take 100% proccessor time, if there are while loops
without waits in it.. But this is only the case when the vi is running.

Anyway, good look with it.

Regards,

Wiebe.


"saverio.mercurio" wrote in message
news:50650000000500000035CA0000-1042324653000@exchange.ni.com...
> This is while I'm editing the diagram.
>
> In case the follow-up question is asked: I have a pretty good machine.
> 2GHz P4, 256MB RAM, with Windows XP. It's not smoking, but it's quite
> peppy.

[saverio.mercurio]

BINGO!

Well, sort of...

It's actually two things. I had MusicMatch running, but not playing. (Processor time was not at 100% for those of you thinking that. It was barely hitting 10% while I was working.) If you quit out of it the context help eventually wakes up. However, I discovered that it's also tied to whether or not the objects you're hovering over are enclosed in some sort of structure, like a case structure, sequence structure, loop, etc. If they are the context help window gets "stuck" and only works correctly if you quit out of MusicMatch. If the objects are just "loose" on the diagram the context help works correctly regardless of whether or not MusicMatch is running. Who'd've thunk?

Definitely something I wil
l forward to NI. Whether or not it's a problem with LabVIEW is a different question.

Much appreciate the suggestion!

-Saverio