When I compile uir screen comes to forground

[menchar]

When I compile one of my files in CVI 8.5 FDS it sometimes forces the UIR tab to open and closes the source file tab ?!

I haven't been able to nail this down, but it might have to do with having used the "find uir object"  from the text editor.  It's like some funky state is hanging in the IDE that re-executes the find uir object function.

Menchar

[Jervin Justin]

Hi menchar,

I was unable to reproduce the behavior you described on my end...

Does this happen on every single project or only on a single project? Does it happen intermittantly or all the time?

Also, what is the output of the compile? Does it fail or is it successful?

Hopefully with a little more information we can try to reproduce the issue narrow down the problem. Thanks.

[menchar]

Happens after I've viewed the .uir file tab and brought up a new tab on a tab control, then go back to a file tab, and compile that file.  Compile succeeds.

And it happens only after the first time you show a particular tab panel on the tab control.

So here it is:

1.  Create a project with a UIR with a panel with a multi-tab tab control on it.

2.  Use the CVI 8.5 window tab mode for windowing the uir and the .c file.

3.  Bring the .c file to the foreground and compile it.

4.  Bring the uir file to the foreground, and select a tab in the tab control that's isn't currently showing.

5.  Go back to the .c file, and compile it.

6.  uir tab is forced to the foreground.

Menchar

[menchar]

If the compile fails, the IDE does show the file tab to display the errors.  Looks like it has the uir tab up momentarily first though. 

If the compile succeeds, you're left looking at the uir tab.

Behavior the same for any .c file in the project.

It happens whenever the uir editor sets the "save required" flag on the uir file.  This happens whenever you bring up a new tab (even though no edit's been made) or if you bring up the edit panel for the tab and cancel out (again, no edit made but save flag set).

So it looks to me like you've got the 8.5 IDE's windowing / saving logic goofed up for the uir editor.  Probably something to do with the 8.5 IDE's tab windowing.

Message Edited by menchar on 05-15-2008 02:13 PM

[KristenC]

Hello menchar,

I was unable to reproduce the behavior you are seeing.  I followed your instructions, I compile, then go to the UIR and select a different tab, then go back to the .c and compile again, but my .c stays in the foreground.  Can you take a look at my project and see if I am missing anything.

Thanks for your feedback.

[menchar]

Yup, not seeing it with your project.

I can't send you my project.

I'll try loading that same project onto a different 8.5 FDS installation and see if it does it there.  Are all 8.5 FDS releases the same build?  Has NI done an incremental update release on 8.5 FDS?

Menchar

[Mert_A.]

Currently, there is only one released 8.5 version of CVI.

Can you reproduce the behavior by following the steps you gave in your earlier post (including creating a fresh project)?

Since Kristen's project did not demonstrate the quirk in your environment, it seems that your particular environment settings/configuration are not involved. Rather, it apparently hinges on something in the project or the workspace. Could you try deleting (back up first, of course) the .cws file that your project is in, then try launching the .prj and see if you can reproduce the quirk again? Do you have multiple projects in the workspace? If so, do the .c or .uir files in question belong to more than one project in the workspace?

Mert A.
National Instruments

[menchar]

Hi Mert -

It doesn't reproduce even on the same install, same project, same workspace today!

Yes it is a multi-project workspace.    The uir and the c files I was compiling to see the flaw were in the same project.

I had used the "find uir object" function to get to the uir from a control callback, I thought at first this was the cause.  I rarely use this feature, and had not seen this particular flaw before.  I had used the inverse function too - view callback from the uir editor.

I had been adding and removing projects from the workspace off and on.  The autosave and autobackup were both enabled.

When the problem was showing, it had absolute correlation with getting the UIR editor to flag the uir file as needing to be saved - i.e. the asterisk showing on the uir file tab.  I tried it maybe 10 times, and every single time that the uir file got flagged to be saved, and I did a clean (no error) compile, it yanked the uir tab to the foreground.

Looks like this is another one of those subtle but rare and annoying 8.5 flaws like the GPF's we were seeing earlier.  BTW, I haven't seen one of those in months now.

Menchar

[Mert_A.]

Well, I guess we'll keep an eye out for it. Since the bug is pretty innocuous and hard to reproduce, it is a low priority.

Thanks for trying, anyway.

Mert A.
National Instruments.