node icon reverts back to old icon when using ns2 mobility script

What steps will reproduce the problem?
1. use a scenario with ns2 scripted mobility, such as sample1.imn
2. before running, change the icon of n9 and n7 to another custom image such as 
router_purple.gif and router_yellow.gif
3. start the scenario
4. the mobility script starts moving nodes, so far everything is fine
5. change the icon of one of the nodes using the command line:
   coresendmsg.py node number=9 icon=/usr/local/lib/core/icons/normal/router_red.gif
6. also change the icon of a node that does not have a custom icon:
coresendmsg.py node number=7 
icon=/usr/local/lib/core/icons/normal/router_red.gif

What is the expected output? What do you see instead?

node n9 and n7 should have red icons; the mobility script moves the node and 
resets n9 to purple, since a custom icon has been defined.

When cored.py generates the node position message from the ns2script, it is 
including the old icon (router_purple.gif). cored.py will need to parse 
messages it receives from elsewhere (coresendmsg.py). node n9 should remain red.

Original issue reported on code.google.com by ahrenh...@gmail.com on 9 Nov 2012 at 5:38

marek-sezemsky / coreemu

node icon reverts back to old icon when using ns2 mobility script #168