That's weird, I wonder if it's an issue with the latest version of TC!?
Are you able to install TC v15.55.53.7?
ok. here is another interesting caveat regarding this issue. let me know if this behavior rings any bells with anyone.
i bring up my browser based app in chrome on my laptop screen and in the object browser of test complete the Page object is grayed out/disabled.
then i simply drag the chrome browser window over to one of my attached monitors, refresh the object browser and now the page is enabled
both monitors have the same display resolution (1920x1080). has anyone ever seen anything like that before within test complete?
What happens if you refresh the browser without dragging it to another monitor?
Marsha_R if the browser opens up on a monitor and the page object starts out disabled then no amount of clicking the refresh button enables it, but . . . .
. . . . here's the latest thing i've discovered. see if this sounds familiar to anyone. with all three screens (laptop and two monitors) connected via the docking station, one of the three screens is designated as the "main" display.
if the chrome browser opens on the main display then the page object in the object browser is enabled from the get go. if the browser window opens on either of the other displays the page object will start out as disabled. i can drag it over to the main display monitor and refresh the object browser and it will enable the page object and then i can even drag it back to one of the other monitors and the page object "seems" to stay enabled (at least for the most part. once or twice it went dark but then came back). i've experimented with changing which monitor is the main and the page object is always enabled IF chrome opens on THAT monitor. if it opens on either of the other two it has to be dragged to the main display before it will become enabled.
is that weird or what? anyone ever hear of or see such a thing?
i think i mentioned it before but it bears repeating that if i close my laptop lid (thereby effectively reducing my monitor count to just two) there is no issue. the chrome browser can open up on the other monitor (not the main display) and the page object will be enabled. its just when there are three monitors involved that i have the issue of the page object not being enabled at chrome startup
until i drag and drop the browser to a different monitor the Page object remains disabled no matter how many times i refresh the object browser in testcomplete. i'm going to see about getting a smartbear tech to set up a webex with me so they can see what's going on. as soon as i get some sort of resolution I will post it here.
