foremost window losing its property

[Dr._Imad]

This is (Reference#566521)and an NI application engineer is investigating the issue.
However, I want fellow LabViewers to shed light into the issue and offer some suggestions.

1) Run the main.vi. With the "set serial port" button True, press the call button. Will call and open the Debug_cntr_mnu.vi, whose front panel is set to modal
if an error is reported because the port no. is not found, the main.vi becomes the foremost window (not the debug_cntr-mnu.vi)
The debug_cntr_mnu.vi should stay in the front.
Note:you have to force it to report the error, by changing the port numbers (in global.vi) to non existing port in your computer

2)With the "set serial port" Set To False
1)From the LabView menu help, make sure th
at the "context-help-window "is open (selected)
2)run the main.vi, press the call button, the debug_cntr_mnu.vi opens safely and will be the foremost window
Till here it is working fine.
Now, put the mouse cursor on the title bar of the "context-help-window". Then the main.vi becomes the foremost window,and you cannot access the debug_cnt_mnu.vi

It is happeneing on my computer sys, Petium 3, and win 2000, LabView 7

[Wiebe@CARYA]

Hi,

Just a warning; this vi generates a blue screen on my w2k machine.

Regards,

Wiebe.

"Dr. Imad" wrote in message
news:506500000008000000ABC30000-1077587809000@exchange.ni.com...
> This is (Reference#566521)and an NI application engineer is
> investigating the issue.
> However, I want fellow LabViewers to shed light into the issue and
> offer some suggestions.
>
> 1) Run the main.vi. With the "set serial port" button True, press the
> call button. Will call and open the Debug_cntr_mnu.vi, whose front
> panel is set to modal
> if an error is reported because the port no. is not found, the main.vi
> becomes the foremost window (not the debug_cntr-mnu.vi)
> The debug_cntr_mnu.vi should stay in the front.
> Note:you have to force it to report th
e error, by changing the port
> numbers (in global.vi) to non existing port in your computer
>
> 2)With the "set serial port" Set To False
> 1)From the LabView menu help, make sure that the
> "context-help-window "is open (selected)
> 2)run the main.vi, press the call button, the debug_cntr_mnu.vi opens
> safely and will be the foremost window
> Till here it is working fine.
> Now, put the mouse cursor on the title bar of the
> "context-help-window". Then the main.vi becomes the foremost
> window,and you cannot access the debug_cnt_mnu.vi
>
> It is happeneing on my computer sys, Petium 3, and win 2000, LabView 7

[Dr._Imad]

Today I ran the vi on a windows XP, Pentium 4, LabView 7, system, and it showed the same behavior.
Now, How did all this happen ?
I converted an application from LabView 6.02 to 7, and started seing that behavior. Similar applications in Labview 5.1, 5, 4.1, 4, 3.1 worked correctly. I also converted the application to version 6.1 and it works correctly too. The application in version 6.02 (whih I still have) works correctly
Only in LabView 7 does the problem pops up
The debug_cntr_mnu.vi is the vi converted from version 6.02 (of course I deleted many extra code from it so I can post it small enough).

[Dr._Imad]

Just to report on the issue further and how I was able to solve the PROBLEM.
After experimenting with many vi settings, eventually I found out by pressing the maximize/restore icon box (Top right border of the vi), and then saving it, the problem goes away (in this case it is the debug_cntr-mnu.vi.
And I also found out that many vi's (converted from version 6.02, front panel set to Modal and size set to "size to screen") exibit the same behavior.
and for some of them, I had to to do what I did (press the maximize icon then save , exit, reload the vi) many times before the problem goes away for a particular vi.

However, this is an issue with LabView 7 express converting vi's from previous versions of LabView (and in my case version 6.02)