A auto-mapper bug in version 4.40 and 4.44

Posted by Ron on Wed 09 Dec 2009 06:12 PM — 7 posts, 25,024 views.

Ron China Wed 09 Dec 2009 06:12 PM #0

Hi , Nick .
Thanks for your mushclient. This is a great program.

I think there is a bug for auto-mapper.

I enabled the mapper it work well on standard direction, but when i add some special direction like "nu/sd", the standard direction stop work. whatever i input any direction.

I think the reason may be "Remove backtracking". because when i disable it the mapper can work well .

Please check this .

Thanks.

Ron

Nick Gammon Australia Forum Administrator Wed 09 Dec 2009 08:08 PM #1

How did you add the special direction exactly?

The mapper expects non-standard directions to be in brackets eg. "(nu)". Otherwise that is interpreted as north followed by up.

Ron China Wed 09 Dec 2009 11:08 PM #2

I used the function 'addtomapper' in perl script.

Nick Gammon Australia Forum Administrator Wed 09 Dec 2009 11:18 PM #3

Can you give a bit more detail? Did you do something like this?


AddToMapper("nu", "sd")

So you want to add a direction called "nu"? If I do that I get a speedwalk:


(nu/sd)

Or do you mean something else?

Ron China Thu 10 Dec 2009 05:58 AM #4

Hi Nick,

I will explain what i did.

First , I add some common direction like n, s by input or number keypad. The auto-mapper work well.

And then , I attempt to add one special direction (nu/sd) , I used 2 way to add them. One is call 'AddToMapper' function by perlscript 'addTomapper ("nu", "sd");send('nu')', another is input some thing into the window GUI for generate special path . On this step. auto-mapper work well too. it can record the special direction.

But the problem happened on next step. when the last item in mapper sequence is (nu/sd), whatever i input or use keypad some common direction like 'w', 'e' , the auto-mapper catch nothing until i delete the special direction.

I have written some perl script in a plugin to solve this. But i think there should be a bug . please have a check.

thanks.

Ron

Nick Gammon Australia Forum Administrator Thu 10 Dec 2009 06:48 AM #5

You are right, this is a confirmed bug.

This particular condition shows up in the circumstances you describe.

Fixed in version 4.45.

Nick Gammon Australia Forum Administrator Thu 10 Dec 2009 08:40 PM #6

Your query about DatabaseStep has been moved to:

http://www.gammon.com.au/forum/?id=9916

Please start a new thread for unrelated questions.