I have 2 monitors to my desktop but QTP understands only the windows on primary monitor ...
My application consists of multiple windows and since QTP needs the windows to be visible and the widgets to be visible.
It is difficult to have all the windows up on the same screen.
Can I spread the windows across these 2 monitors and QTP to take care of this dual monitor issue ?
If yes how ?
QTP does not support dual monitors, this can be verified by mercury support. I too use dual monitors so i am aware of the problems QTP has with that.
As long as QTP can identify each browser window independantly then you should not have any problems running everything on one monitor. When QTP needs to interact with one of the browsers it will bring it to the front on it's own. If not then you can set focus on that window via script and then interact with child objects
You may need to set up your object repository so that each window is identified individually.
For example you may need to use the openurl and/or the Ordinal identifier CreationTime to differentiate your browser windows.
You should be able to get your stuff to work on one monitor you just have to help QTP determine which window it needs to be working with when it needs to interact with an object in that window.
I used two monitors with QTP 9.2 for several months earlier this year. Search the forum for "dual monitor" or "two monitor", etc. and you will find a post where others told me the ins and outs of using dual monitors.
While it is not trouble free, you can get QTP (at least version 9.2) to work with them. I think you need to have the application under test running on the Primary monitor and QTP on the secondary--which is how I did it. I was even able to move my toolbar (sometimes with difficulty) to the secondary monitor so it "sticks" through boot.
Anyway, it works well enough that your time invested to experiment won't be wasted.
I also do this like Terry Horwath states: all AUTs on primary monitor; QTP on secondary (could be either). QTP was unable to interact as required with AUTs or objects on the secondary monitor, and I never have heard of any way to get this to work.