Unable to add nodes in EasyEdit mode

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Add a new node in EasyEdit mode

What is the expected output? What do you see instead?
- An new node should be created but nothing happens.

What version of the product are you using? On what operating system?
- latest Vespucci version (14.02.2013), however the bug appeared already with 
an eralier version
- Android 4.2.1

Please provide any additional information below.
- Obviously, no other functionality of Vespucci seems to be limited. 

Original issue reported on code.google.com by jost.le...@gmail.com on 17 Feb 2013 at 3:29

[GoogleCodeExporter]

Unable to reproduce. Did a survey today which included creating new nodes and 
ways - worked fine. Note that when OpenStreetBugs is enabled, you have an extra 
step - tap the plus icon in the toolbar (next to the bug icon) - before nodes 
appear.

Original comment by andrew.g...@gmail.com on 18 Feb 2013 at 9:39

• Added labels: Component-UI, Usability

[GoogleCodeExporter]

Maybe something is wrong with my system or Vespucci installation? However, I 
reinstalled it without any change.

- Adding nodes with OpenStreetBugs enabled is working (thank you for the hint, 
I can bypass the issue for now)

- Adding nodes in EasyEdit with OpenStreetBugs disabled is not working with my 
installation. Any chance to debug?

Original comment by jost.le...@gmail.com on 18 Feb 2013 at 4:27

[GoogleCodeExporter]

Original comment by andrew.g...@gmail.com on 19 Feb 2013 at 4:13

• Changed state: Accepted

[GoogleCodeExporter]

(where did all my typing go?) Reproduced on 4.1.1 tablet. Will investigate 
later this week/weekend.

Original comment by andrew.g...@gmail.com on 19 Feb 2013 at 4:18

[GoogleCodeExporter]

I don't know if this helps, but in my case this bug manifests on my TF700T 
tablet (Android 4.2) even though I still feel the vibration feedback. IOW, if I 
long-press, I feel the vibration, but no new node is created.

Original comment by giuseppe...@gmail.com on 20 Jul 2013 at 6:46

[GoogleCodeExporter]

It seems as if this is (unintentionally) fixed in the 0.9 builds. Could we get 
more confirmation that this is the case so that we can close this issue?

Original comment by sp8...@gmail.com on 27 Jul 2013 at 12:09

[GoogleCodeExporter]

With the 0.9 beta, I cannot reproduce the bug anymore. I vote to close the 
issue. 

Original comment by jost.le...@gmail.com on 28 Jul 2013 at 8:32

[GoogleCodeExporter]

This is fixed for me too on 0.9 beta.

Original comment by giuseppe...@gmail.com on 28 Jul 2013 at 9:20

[GoogleCodeExporter]

Original comment by sp8...@gmail.com on 28 Jul 2013 at 9:27

• Changed state: Fixed