Hi Ara,
Apologize for my delayed response. Got busy with VMware Workstation 7.0
release. Will be released by next week.
Have fixed these in LDTPv2, will check in the code tonight.
Now, hasstate, getallstates can recognize the menu hierarchy, though the
last object in the menu will be checked for
Nagappan,
I agree with Ara. Personally, I feel it is always more comfortable to
address any menu in the full hierarchy. The 'mnuCloseAll1' tip you give is
working. But it requires a bit of logic from user's code to follow LDTP's
naming convention on the anonymous objects. But for menu, full hierar
Hello all,
I've always found the way LDTP deals with menus a bit weird.
I think it is much better if all the functions dealing with menus would
use some kind of hierarchy. Or better, if it could be set in the parameters:
ldtp.doesmenuitemexist(windows_name, "mnuFile;mnuCloseAll", hierarchy=true
Hi Scott,
On Wed, Oct 14, 2009 at 4:02 AM, Wang Qi, Scott wrote:
> Hi Nagappan,
>
> I saw some inconsistency in the parameter when calling these two functions
> : hasstate () and doesmenuitemexist().
>
> 1) ldtp.doesmenuitemexist(windows_name, 'mnuFile;mnuCloseAll')
>
> doesmenuitemexist () requ
Hi Nagappan,
I saw some inconsistency in the parameter when calling these two functions :
hasstate () and doesmenuitemexist().
1) ldtp.doesmenuitemexist(windows_name, 'mnuFile;mnuCloseAll')
doesmenuitemexist () requires the full path which is the
'mnuFile;mnuCloseAll' menu.
2) ldtp.hasstate(win
