What steps will reproduce the problem?
1. Create a script called, say, "foo.py"
2. Scan a barcode for a (possibly different) script, also called foo.py
What is the expected output? What do you see instead?
I expected sl4a to warn me that I was going to replace the current foo.py
script. Instead, it silently overwrites the old with the new one.
What version of the product are you using? On what operating system?
SL4A r0
I'm not sure if that's the intended behaviour, and it hasn't bitten me in any
way, I just realised that it might be confusing.
If you agree that a warning is the preferred behaviour, I could provide a patch.
Original issue reported on code.google.com by tioerre on 5 Aug 2010 at 5:57
Original issue reported on code.google.com by
tioerreon 5 Aug 2010 at 5:57