Search found 4 matches
- Tue Sep 10, 2013 4:29 pm
- Forum: Bug Reports
- Topic: Ranorex 4.1 Bug - Object Spy Tracking keys are not working
- Replies: 1
- Views: 2112
Ranorex 4.1 Bug - Object Spy Tracking keys are not working
When I am tracking an object using the Object Spy within my Ranorex project, I noticed the following issues: 1. Holding down F12 does not pause tracking so I can get to a right-click menu. 2. Pressing the Esc key does not cancel tracking. I have to click on an object. 3. Instant tracking is not bein...
- Wed Dec 12, 2012 6:31 pm
- Forum: Automation API
- Topic: Change the reporting level of Validate.Attribute false?
- Replies: 6
- Views: 3749
Re: Change the reporting level of Validate.Attribute false?
Turns out I wasn't originally using a button object, which is why I couldn't see the Visible attribute. Once I looked for a button it worked perfectly. Thanks guys!
- Wed Dec 12, 2012 4:05 pm
- Forum: Automation API
- Topic: Change the reporting level of Validate.Attribute false?
- Replies: 6
- Views: 3749
Re: Change the reporting level of Validate.Attribute false?
Hi Ciege, I thought that's what I was doing by validating the object was visible in my code. Is there another methode I can call from the repo object called "Visible"? I'm not seeing it - only "UseEnsureVisible" which I don't want. Markus, the Validate statement I'd like to use is Attribute(RepoItem...
- Tue Dec 11, 2012 10:51 pm
- Forum: Automation API
- Topic: Change the reporting level of Validate.Attribute false?
- Replies: 6
- Views: 3749
Change the reporting level of Validate.Attribute false?
Is ther any way to force a Validate.Attribute failure into a warning? Here's what I'm using it for. I need to click a specific object depending on how a screen is rendered. All the objects in question Exist (which is why I can't use Validate.Exist) but they are visible or not, depending on what scre...