BrianAlford
Occasional Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: properties missing from object inspector
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.2.2KViews0likes4CommentsRe: properties missing from object inspector
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).2.2KViews0likes6Commentsproperties 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 that has all of the usual properties (txtStartDate) and one that is missing these properties (txtDateClosed). An error occurs when the program cannot find the Locked property of txtDateClosed. The controls are both of type ThunderRT6TextBox. Both are on the same panel on the same form. txtStartDate has a NativeVBObject property and a category of properties called Visual Basic which txtDateClosed does not have. I have checked in the source code and both controls are standard textboxes. Does anyone have any idea why these properties are present on one text box and not the other? Update: 1. The application is a legacy application written in VB6. 2. The problem is occurring with combo boxes as well. 3. The problem does not occur consistently - sometimes controls that normally have these properties available no longer do so. 4. The same version of the executable is being used. I have not recompiled the application.2.3KViews0likes8Comments