smurg
2012-01-03 03:56:55
I'm making my own Bank withdrawal method via DTM's and am incorporating OptionsExit to tell if I need to Withdraw-X or not.
Withdrawal itself semi-blows because it only does WaitOptions and re-right-clicks to get the menu for Withdraw-X. (It only happens once and then the -X will be -# and it won't matter, I know, yada….)
Anyways OptionsExist's descriptions is "Returns true if an Option in txt is found in the RS Option Menu. Will move or do nothing according to the boolean Move"
So I do OptionsExist(['whatever', 'adsa'], False)
Yet, it uses ChooseOptionMultiEx which has at the end
The whole purpose of using OptionsExist and setting the Move boolean to False is to keep the menu up. Yet, it clicks the 'Cancel' option.
Wouldn't this be more appropriate:
Withdrawal itself semi-blows because it only does WaitOptions and re-right-clicks to get the menu for Withdraw-X. (It only happens once and then the -X will be -# and it won't matter, I know, yada….)
Anyways OptionsExist's descriptions is "Returns true if an Option in txt is found in the RS Option Menu. Will move or do nothing according to the boolean Move"
So I do OptionsExist(['whatever', 'adsa'], False)
Yet, it uses ChooseOptionMultiEx which has at the end
if (not result) then
ChooseOptionMultiEx(['Cancel', 'ancel', 'ncel'], 'All', clickLeft);
The whole purpose of using OptionsExist and setting the Move boolean to False is to keep the menu up. Yet, it clicks the 'Cancel' option.
Wouldn't this be more appropriate:
if (not result) and (Action <> Nothing)then
ChooseOptionMultiEx(['Cancel', 'ancel', 'ncel'], 'All', clickLeft);