| || |
Problems with Robot correctly identifying toolbars created wi
User Dmitry Shevchenko (DShevchenko@lanit.ru.nospam) posted:
If you are not testing the toolbar itself, just use the appropriate menu items. Your script will be more readable and robust.
Re: Problems with Robot correctly identifying toolbars created wi
User Yeager, David (KIvanov@STSSystems.com.nospam) posted:
That's the way PB toolbars are. We always use the menus in our scripts (and
put those menu calls in separate scripts, so that if the menu changes, you
only have to change the scripts once), and we will test the toolbar 1 time
at some point to make sure that it actually works -- however, it is
coordinate dependent, so if the toolbar button is moved, you'll have to
update your script
Quality Assurance Supervisor
Enterprise 2 Applications
STS, an NSB Company
Tel: (514) 426-0822, ext. 2175
From: "Yeager, David" <email@example.com>
Date: Mon, 6 May 2002 15:21:35 -0400
I'm working on an app created with powerbuilder. Robot is identifying the
app's toolbar as generic...
Window SetContext, "Name=w_fortracs_frame", ""
GenericObject Click, "Class=FNFIXEDBAR;ClassIndex=1", "Coords=44,16"
I also received this when I use the Inspector to look at the object and
seeing the same problem.