Bug fix to allow schedule use

[roshii]

These simple fix allows one to use schedule files with sendpayment.py

[AdamISZ]

Thanks for the contribution.
I will do some testing in a moment, but, on a first read through, I don't understand the logic: the former version sets the variable mixdepth to the maximum used in the schedule, and then the actual max mixdepth passed into the wallet constructor is the maximum of that, and the options.amtmixdepths ; your new version seems to only read the first entry in the schedule? So it would only work with schedules of length 1? (as opposed to use of a schedule file with the -S option?

[AdamISZ]

OK, after careful examination I saw that basically one recent PR broke custom schedules, so fixed that. See d9bcca3 .
Sorry for not merging your code but it would have taken much longer to first change it so it made sense, then rebase, then merge the PR than just fix the bug.

[roshii]

your new version seems to only read the first entry in the schedule? So it would only work with schedules of length 1? (as opposed to use of a schedule file with the -S option?

I wrongly considered that sendpayment.py was meant to send a single payment and as such did not see we it should look further in the file.

No bother for not merging my code, I just did not had the full understanding of script purpose. I'm glad it allowed to fix some issue anyway :)