The Following User Says Thank You to dragly For This Useful Post: | ||
|
2010-08-05
, 22:43
|
Posts: 252 |
Thanked: 252 times |
Joined on Nov 2009
|
#402
|
|
2010-08-06
, 11:46
|
Posts: 111 |
Thanked: 80 times |
Joined on Oct 2009
|
#403
|
|
2010-08-06
, 14:39
|
Posts: 252 |
Thanked: 252 times |
Joined on Nov 2009
|
#404
|
|
2010-08-07
, 12:12
|
Posts: 1,994 |
Thanked: 3,342 times |
Joined on Jun 2010
@ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
|
#406
|
|
2010-08-07
, 12:50
|
Posts: 252 |
Thanked: 252 times |
Joined on Nov 2009
|
#407
|
Well... I have got mbarcode 0.2.1-1. It works well, but I would suggest some changes.
First, why fps are changing when lens cover is closed? What kind of superfluous activity is going on when the camera is closed?
Second, could you give some delay time for the user before the scan itself so that he could understand what does the camera see? It's not necessary; but in the beginning of the scan I can hardly understand what the camera sees.
Third, does the mbarcode know what type of code it scanned? Can it say it: the barcode scanned was EAN (just an example), first three digits show that the country is ..., etc? It could be an addition for mbarcode; for instance, XML files could be used for storing information about meanings of different values of the bar-codes.
Fourth. Does mbarcode try to connect to Internet to get more information about the barcode? If yes, could it be separated into an optional extension: some people would prefer not to use it?
The Following User Says Thank You to dragly For This Useful Post: | ||
|
2010-08-07
, 15:19
|
Posts: 29 |
Thanked: 12 times |
Joined on Apr 2010
@ ~
|
#408
|
|
2010-08-07
, 15:44
|
|
Posts: 909 |
Thanked: 216 times |
Joined on Nov 2009
@ Bremen, Germany
|
#409
|
|
2010-08-07
, 17:52
|
Posts: 252 |
Thanked: 252 times |
Joined on Nov 2009
|
#410
|
pure qt app: 1.9 s
mbarcode (lens cover closed): 5.4 s
mbarcode (lens cover open): 9.2 s
There's nothing scientific here, just me starting the application from terminal and running a stopwatch a couple of times. The numbers are an approximate mean value.
In other words. It takes almost ten seconds to start scanning, and over 5 seconds before the user sees any activity. This should be lowered significantly. I'm going to look for some possible enhancements now.
Last edited by dragly; 2010-08-05 at 22:41.