key focus is not visible for all objects when tabbing

[BigBen]

I'm using LabView 5.1.
The key focus is not visible for all objects when tabbing through a "disabled and grayed-out" object.
For example, let's say I create a panel with 3 buttons. If I create a "disabled" attribute for button 2 and assign the value "2" (disabled and grayed-out) to it. When I will run this VI, the key navigation will go through button 1 and button 3 (skipping button 2 as expected) but the key focus on button 3 will not be visible.

Is this a bug with LabView or am I doing something wrong ?

[Ben]

Hi BigBen,

It does not sound like you are doing something wrong.

Quick question,
If you minimize and then maximize the screen (when the key focus is not visable), does the desired button now show as selected?

If so, I would suspect a video driver issue (wrong version, down rev. etc).

Ben

[BigBen]

Hi Ben,

No, the button still show as unselected even if I minimize and then maximize the window...

Quick question, should I conclude that you don't see the same behavior on your side ? Do you use LabView 5.1 ?

Benoit

[Ben]

Hi BigBen,

I am currently consulting on-site and did not have time to re-create the VI you described. I was just sharing a quick idea.

If you post an example VI (as 5.1) I will try it the next time I get back to my machine (LV 5.1.1, BV 2.1.1 LV-RT 6.0.3, and LV-DSC 6.1).

NI support should be able to help if time is an issue. (you know, gotta feed the wife and kid and all).

Ben

[BigBen]

Hi Ben,

Don't worry, time is not an issue... I'm posting an example of a VI with the problem I described. I noticed that the problem occurs only with "dialog buttons".
When you have time, let me know if you see the same behavior. If you do, I will report the problem to National Instrument.

Thanks for your time !

BigBen

[wiebe@CARYA]

Ben,

I checked 5.1.1 and 6.0.2 (didn't even know there was a 6.0.3?). I cannot
reproduce the problem...

Regards,

Wiebe.

"Ben" wrote in message
news:5065000000050000001F810000-1023576873000@exchange.ni.com...
> Hi BigBen,
>
> I am currently consulting on-site and did not have time to re-create
> the VI you described. I was just sharing a quick idea.
>
> If you post an example VI (as 5.1) I will try it the next time I get
> back to my machine (LV 5.1.1, BV 2.1.1 LV-RT 6.0.3, and LV-DSC 6.1).
>
> NI support should be able to help if time is an issue. (you know,
> gotta feed the wife and kid and all).
>
> Ben

[BigBen]

Hi Wiebe,

I'm using LV 5.1.1 with LV-RT 5.1.1.

I didn't know that LV-RT 6.0.2 was compatible with LV 5.1.1. I thought that version 6.0.2 of the Run-Time Engine may only be used to run executables that were built with LabVIEW 6.0.2.

BigBen

[BigBen]

Hi Wiebe,

I'm using LV 5.1.1 with LV-RT 5.1.1.

I didn't know that LV-RT 6.0.2 was compatible with LV 5.1.1. I thought that version 6.0.2 of the Run-Time Engine may only be used to run executables that were built with LabVIEW 6.0.2.

BigBen

[wiebe@CARYA]

Ben,


What you say is true, I ment I checked it with LabVIEW 5.1.1 and LabVIEW
6.0.2. Both with there own RT engine... I didn't check executables, only
vi's...

Does the problem only occure when you build an executable?

Regards,

Wiebe.

"BigBen" wrote in message
news:50650000000500000038810000-1023576873000@exchange.ni.com...
> Hi Wiebe,
>
> I'm using LV 5.1.1 with LV-RT 5.1.1.
>
> I didn't know that LV-RT 6.0.2 was compatible with LV 5.1.1. I
> thought that version 6.0.2 of the Run-Time Engine may only be used to
> run executables that were built with LabVIEW 6.0.2.
>
> BigBen

[BigBen]

Hi,

I didn't try it with an executable.
LabView support said they knew this problem and that it was fixed in LabView 6.

Thanks,

BigBen