LabWindow/CVI 8.5 won't start anymore

[YannickW]

Hello Luis,

I may have change the screen resolution...

Thanks,
Yannick

[LuisG]

Hello Yannick,

Actually, we have found the sequence of actions that cause this bug to happen:

1. Maximize the main CVI wokspace window
2. Move the vertical splitter bar far to the right, fairly close to the right edge of the window
3. Exit CVI, without de-maximizing the window.

When that happens, the next time you start up CVI, you will see this error. This is because the window sizes that are stored in the registry are the normal (non-maximized) window size. Yet, the position of the splitter bar is stored relative to the current (maximized) window size. In cases where the splitter bar is moved far enough, in the maximized window, such its offset from the left edge of the window exceeds the entire width of the nomal (non-maximized) window size, this bug will occur.

This will be fixed in the next version of CVI. Thanks for helping us find the cause!

Luis

[AMM]

Hi,

I just had this same problem!  I modified the registery value you suggested and now it's working again.  I saved my registry before the change so if you would like a copy just let me know.  FYI: The last project I had opened was a very old .prj file (probably created with version 7?) - could be a clue?  I didn't move the splitter bar, but the IDE was maximized (I think).

AMM

Message Edited by AMM on 05-20-2008 12:19 PM

Message Edited by AMM on 05-20-2008 12:21 PM

[LuisG]

Hello AMM,

Given that you had CVI maximized when the problem happened, it's very likely that the bad registry values were caused by this same problem, and so there's no need to investigate further.

It's possible that there might be other ways of getting into that state without having to move the splitter bar. Essentially the problem happens when the "normal" (non-maximized) size of the workspace window is smaller than the area to the left of the splitter bar, when the window is maximized.

Now that you've fixed up the registry value, this will probably not happen again to you (I think it's a pretty rare problem). But if does happen again, you can always fix it by doing what you did now.

Thanks for reporting it!

Luis