What is the little square?

[Steven_T]

Hello all,

I have noticed that an overwhelming majority of the computers with two monitors at NI do not have the square anomaly.  The one computer I have found that does have it has a NVIDIA Quadro FX 540.  It has a slightly older driver version (checked in Device Manager) of 7.7.5.6 for NVIDIA Quadro FX.  We tested this same card on another computer and with driver versions 9.1.3.6 did not display the anomaly. 

The computer's owner was not around so we have not had the chance to see if upgrading the drivers on the affected computer makes a difference.  Some more data points including video cards and driver versions could help with the situation.

I hope this helps.

Steven T.

Message Edited by Steven T on 11-03-2006 05:05 PM

[GPIB_Guru]

Okay, I did some experimenting this morning. I know what the problem is. In the NVIDIA control panel, they have an option to "Prevent windows from opening off-screen". If this option is enabled, the dot appears. If this option is disabled, the dot does not appear. I am guessing that the LV RTE launches something offscreen that has a size of 0,0. I don't know what it is used for, but normally it is "hidden" by being off-screen. WIth my video card set to now allow things to open off-screen, I see it.

Steven -> Can you see what the settings are on the computers that you are looking at?

[RobCole]

I am using an Nvidia GeForce 6600 graphics card with do not allow windows to open off screen turned on. Since other people here use a different monitor configuration (the people with laptops have their 2 screens arranged vertically while my system uses the 2 screens horizonal), I need this turned on or some LabVIEW windows appear as only a thin line at the edge of the screen.

I keep my video driver up to date and have noticed this small square through at least 2 video driver updates.

     Rob

[kehander]

Just an idea...

I am familiar with numerous Windows programs that can be used to get information about currently visible windows. (ShoWin from FoundStone comes to mind.) Perhaps you can use such a program to get more information about this supposed window?

[GPIB_Guru]

Using ShoWin, I went over the Main LabVIEW title screen (for 7.1) and my little square and got the following:

// This is the main LV Application
Title:    LabVIEW
Class name:    LVDChild
Window handle:    789368 (0x000C0B78)
Parent window:    0      (0x00000000)
Owner window:    134358 (0x00020CD6)
Window ID:    0      (0x00000000)
Window proc:    0x00000000
Client coords:    x:   0 y:   0  w:2560 h:1024
Window coords:    x: 337 y:  14  w: 552 h: 402

// This is my little square:
Title:    LabVIEW
Class name:    LVFrame
Window handle:    658292 (0x000A0B74)
Parent window:    0      (0x00000000)
Owner window:    0      (0x00000000)
Window ID:    0      (0x00000000)
Window proc:    0x00000000
Client coords:    x:   0 y:   0  w:2560 h:1024
Window coords:    x: 635 y: 480  w:  10 h:  10

[Steven_T]

GPIB Guru,

Thanks for all of your work on this issue.  I believe I have more than enough information for further escalations.  Since the work around does not work for laptop users, I will see if there are any other ways to get around the anomaly.

Steven T.

[Travis_M.]

This was reported to R&D (#4369SHU9) for further investigation.

[AlanGrwd]

Just to clean up my original post a bit, device manager identifies my display adapter as an NVIDIA Quadro PCI-E Series and the adapter properties provides Quadro NVS 280 PCI-E as the chip type.

The work-around works without any other apparent impact.

Thanks,

Alan

[hummingbird]

everyone,

can you tell me more about the LVDChild??? Do you known how to send a message the the button on the Lv.exe and control the button in another vc.exe (built by VC++)??

thanks

[bburress]

Hey hummingbird,
    I'm not sure I fully understand your question.  Are you wanting to send a command from LabVIEW to another .exe or from another .exe to LabVIEW?