Android Question VBWep output to log

[drgottjr]

Must the results of the VBWep scan be sent to the log? It seems like a debugging statement left in the final code. Can this be removed? If I knew for sure that the output was deleted from the device when the app closed, it wouldn't matter so much. Thanks.

-go

 

[MarcoRome]

Must the results of the VBWep scan be sent to the log? It seems like a debugging statement left in the final code. Can this be removed? If I knew for sure that the output was deleted from the device when the app closed, it wouldn't matter so much. Thanks.

-go

Can you write more details pls

 

[drgottjr]

please refer to attached screen cap. when you use the VBWep library to scan for wifi ap's the result(s) go to 2 places:
1) a list is returned to the user in line 111 ("Buffer = MyWiFi.GetWifiList") of the sample, and
2) the results are also sent to the log (see right-hand side of attached image).

since the log is generally not available or of any use to average users, showing the scan results in the log seems like it is something a developer would do when debugging his app. later, that step would be removed in the distribution. i looked for the B4A statement in the example and could not find it, so i'm guessing it's embedded in the library's .jar. i was wondering if it could be removed (by someone who works with eclipse or the android sdk) and the .jar recompiled?

if the system deleted the log every time the user closed the app or powered down the device, then it's not a big problem. but if someone uses the library often, and the log kept getting larger, a lot of space would be used up. i believe android maintains several types of logs, but since a normal user would not know how to find them (or be aware that he needed a rooted device to access/delete them), it seems that it would be better not to have the results written to the log. thanks.

-go

 

[drgottjr]

so, just to follow up, I found the .class in the .jar and decompiled it and removed the log calls (almost every other line of code was a call to the log) and used erel's slc to put it back together. i had to tweak the .xml file a little, but it works fine. i call it VBWep-lite. the original author of VBWep hasn't been to the forum for 2 years, so i wasn't sure what else i could do. i'm happy to burn my version if he would remove the log calls and re-post.

for those who may have shared my concern about the log entries, i can post my version. my purpose in using the original library had to do with its ability to scan while wifi is off. that is big. and something that i can't seem to get ABWifi to do. regrettably, wep-secured access points are hard to find in these parts, so that part of the library has little purpose any more.