properties missing from object inspector
Hi, The object inspector and test complete are missing several properties from a text box on one of my forms. In the attached image I have a screenshot of object inspector with two controls, one ...
Forum Discussion
Just a guess, I don't work with anything written using VB6 ....
Could this be something to do with the control being enabled, or not, at the point you inspect it?
Does the Closed Date box only enable once the Start Date box is populated? It may be doing something to the control to disable it in the meantime which is disabling/removing some of the properties. If you get sporadic instances where this happens on other controls, it may be that they are sometime trying to be used before they're fully enabled? If it is, you may need to build yourself some sort of little helper function which checks these types of controls are fully enabled before you use them.
As I say, just a guess, but it reads like this type of problem ....
Hi,
I appreciate the answer but I don't think this is the case. As you can see in the screenshot (4th property from the top) both of the example controls have enabled set to true.
I would also be surprised if being enabled or not limited access to other properties. I could understand if I were trying to set the text value, but I am only trying to read the locked value. In fact, all of the controls I am having this issue with are enabled (and I also happen to know that in the cases I have looked at, they are unlocked).
Ah well. Was just a guess.
Although, just because enabled is set to true, is no guarantee it is actually enabled. I have controls like that. They report they are enabled (and also sometimes visible) when they're not. It depends on the methods the devs have used to disable/hide something. In my experience, they can come up with all sorts of weird and wonderful ways of doing it! Just to confirm, if you try and use the control manually at the point you're inspecting it, it is definitely active and enabled yes?
(Reason I'm persisting with this line is a "Closed" type textbox is often closed/hidden/disabled/locked until the "Start" field contains a valid value ... and they may have done this in some funky way which TC is not picking up .... it happens.)
In the case of the textboxes in the screenshot, both were enabled and not locked (I was able to put data in them).
The problem is not so much the values of the properties and whether they are being accurately reported is that TestComplete is simple not detecting that these properties exist - the algorithm for determining an objects native type must be slightly off.
Maybe I should try aliasing them to access the properties instead of accessing through the Sys.Processes.
Don't think mapping them should make an difference. But you never know I suppose.
The only thing that turned up which sounds sort of similar was this:
Don't suppose any of that applies to yours? (it sounds like yours only do this intermittently as well .... which does sound more like a TC problem if it's not due to the current state of the control)
