Develop Bugs

[APP][ALPHA] G Force Logger for Vehicle Performance (no, not gPC)

Hi, my name is Eric. I've been working with WinCE for a long time (since WinCE 2.0 haha) and I've regained interest in PPC programming. Working with few things here and there, mostly experimenting.
In anycase, I've got an idea to record g forces on a vehicle while it's being tested to its limits (AutoX, drag race).
Now, I know there's already a piece of software out there, gPC, but it isn't completely refined (indepth calibration, angle corrections) or completely free (by donation).
The goal of the project is to create something similar to a device called gTech which goes upwards of $300 for the basic model.
Key features will include:
- a reset function + algorithms to compensate for device orientation
- graphs of resulting logged data
- logging of calibrated data and raw data
- Driving aids
- Flashing screen to indicate reaching of new peak G (separate indicators for forward and lateral)
- a screen showing realtime overlapping graphed data for all axis
- a 2d grid with a cursor indicating current forward and lateral g
- on the same 2d graph, a drawn boundary indicating limits of g achieved (this will eventually look like an egg after working the car hard)
- and finally, real time telemetry transmission via edge/3g to a receiving computer
The ultimate goal of this project is to provide reliable data for motor enthusiasts whether they would like to see if their shifting is smooth, or if they're braking, or powering on in the right places or if their car mods have had any effect (this last one is pretty useful to quantify). In addition, provide some rudimentary tools to assist in competitions and spirited driving in the form of g limit warnings (flashing screen, large indicators of current g). In the case of spirited driving on a mountain road, the device can warn when approaching loss of traction (after collecting limit data) to prevent going off a cliff.
Venues of use:
Auto Cross
Track Days
Drag Strip
Skidpad
Of course, I have to insert here, that this device can't save your bacon if you do something idiotic and by no means do I condone dangerous driving.
With that said, all the above is what I hope to achieve and any of your comments is well appreciated.
Current Release:
v0.1
Alpha stage, rudimentary raw data output via numbers and a line (indicating X and Y recorded g) and a circle (indicating Z g). The numbers shown are the raw numbers recorded from the accelerometer and not converted to m/s^2. Although, you can probably do that math on your own if you're smart enough (simple scaling). What I've discovered is that each accelerometer is different, and even going from a negative axis (eg, device upside down) to positive axis (device right side up) will give different numbers. In addition, if you run the program, you'll notice a lot of jitteriness. I hope it doesn't affect the accuracy once I smooth them out with a segmented average.
Executable is packaged in a zip. It contains an EXE which can be straight run with Dot NET CF v2.0 (basically, all WM 6.1 devices)

Hi Canagan,
Great idea, I will certainly be testing this out.
I would like to ask, would it be possible to be able to include 1/4 mile time, and 0-60 etc so we can work out HP of the car. There is a similar app for the Iphone called Dynolicious http://gizmodo.com/5030749/iphone-apps-we-like-dynolicious-car-performance-meter
Thanks.

Whoooaaa sound a really good app ! Will test it this weekend ! Thanks

PooleyUK said:
I would like to ask, would it be possible to be able to include 1/4 mile time, and 0-60 etc so we can work out HP of the car. There is a similar app for the Iphone called Dynolicious http://gizmodo.com/5030749/iphone-apps-we-like-dynolicious-car-performance-meter
Click to expand...
Click to collapse
Yes, I can do that if there's more of a demand for it. Calculating horsepower is fairly simple, however, I may put 1/4 mile times and 0-60 towards the end of development as they require tieing into the GPS.

Great idea.. I will test it also
It seemt to be working on my Touch HD. But are the meaning of all these numbers??

CanaganD said:
Yes, I can do that if there's more of a demand for it. Calculating horsepower is fairly simple, however, I may put 1/4 mile times and 0-60 towards the end of development as they require tieing into the GPS.
Click to expand...
Click to collapse
Cool, looking forward to seeing this develop.
So far the accelerator test seems to be working fine.

would be need ive i could see how many hp mycar has

Transparent controls in native WM apps

Hey all,
I've been searching for techniques people use to make transparent controls. The problem with windows mobile is that windows always have the CLIPCHILDREN window style set. So you can't grab the contents of the parent window (in WM_ERASEBKGND for example) because it isn't there.
One technique would be to have the parent pass the handle of the background DC it uses to the child control but that involves having a memory DC around all the time. And if the child control is covering any sibling controls you'd be out of luck as well.
Another solution I've read about is to temporarily hide the child window so the parent window is forced to redraw the parts that would normally be obscured by the control. I personally do not like this approach. (the drawbacks are also discussed on some MS forum, i'm not allowed to post outside links yet, google for "Rounded Buttons : Does any one see any problems with this method" and you will find it)
So, there are ways to achieve what I'm looking for but they are far from optimal. Just wondering what everybody else is doing to achieve this.

The responses in that thread are pretty much spot on (funny to find I know over half the posters in that thread by reputation).
If you want to do this well, you really need to draw your own stuff, making a complete custom UI.
There is no proper way to do this in Windows Mobile (without runtime kernel patching, that is ).

Chainfire said:
The responses in that thread are pretty much spot on (funny to find I know over half the posters in that thread by reputation).
If you want to do this well, you really need to draw your own stuff, making a complete custom UI.
There is no proper way to do this in Windows Mobile (without runtime kernel patching, that is ).
Click to expand...
Click to collapse
What do you mean by "drawing your own stuff"? I am drawing everything myself now in all control i made using AlpheBlend() where needed. But that still doesn't resolve the background issue. Or are you referring to just drawing everything in a single WM_PAINT handler and only having one screen DC?

PegNosePete said:
What do you mean by "drawing your own stuff"? I am drawing everything myself now in all control i made using AlpheBlend() where needed. But that still doesn't resolve the background issue. Or are you referring to just drawing everything in a single WM_PAINT handler and only having one screen DC?
Click to expand...
Click to collapse
Well the method I use in my own new UI's is indeed per form (excluding WinAPI controls like edit boxes and such) draw using only one DC.
The problem is that any 'windowed' control, the parent will not draw to the DC if a 'windowed' control overlaps. Due to CLIPCHILDREN all data drawn to that position is simply lost.
Now, handling WM_PAINT you can get the entire update region, which tells you which parts of your form have to be redrawn. You must use this information, because blitting the entire form is very slow!
In essence, to do this right you well end up faking most of the GDI system, including your own 'fake' child windows, invalidating and revalidating portions, calculating the intersections of your 'fake' invalidated regions of the screen with the update region you get in WM_PAINT and redrawing those parts.
There are several different strategies to go about this, one is to redraw on demand, another one is to use double buffering.
I personally mostly use the double buffering technique, as this easily provides every 'fake' control with a bitmap of it's own region. A child control can then alphablend using the parent's buffer as one of the alphablend sources.
You can of course combine this with keeping state information whether a child, grandchild, etc is using alpha / transparency and this with an algorithm deciding which control needs double buffering or can draw on-demand, which can give both speed and memory use advantages. In a lot of situations you can then suffice with only double buffering the 'top' component (form) and a select number of child components.
Of course two drawbacks of per-control double buffering are speed and memory use. You can eliminate the complete-form double buffer with some smart coding and calculating. This will give you a slight speed and memory advantage. Memory use is high because many of your controls will have a copy of their current state.
This can be as complicated, feature-filled, fast and efficient as you are willing to make it. The better you can design the code the better it will work, but it is not a trivial task. There are many ways to go at this, no one way is definitely better than the other ways. It depends on what your applications does with it's display, how simple you are drawing (are you making a simple white background, or a background based on images for example gradient?), which method is more efficient.
The other method is getting the update region and actually perform redrawing of those invalidated sections (instead of copying from buffer). I can tell you from experience that if you are using image backgrounds and alphablend calls, this will be _much_ slower than double buffering (if done right).
I know all of this probaby makes little sense, I'm not a hero with explaining things ... you really have to figure this out for yourself, I guess.
Other advantages of building your own UI system are that if you do it smartly and buffering, it is very easy to port to directdraw, and possibly even GL. But I must warn you, on far the most devices actually using directdraw for this stuff is not much faster, it is in fact hardly noticable. If you manage to make a GL port, that can especially on older HTC devices (pre-HD2) be much faster.

HTC Calculator giving wrong results

Hi
I love my desire. The HTC calculator is nice with the finger friendly buttons with haptic feedback, and I love the fact it's respecting the operator priorities. But what's wrong with the calculator?
100 - 99,9 = 0,09999999999999999
100 - 99,8 = 0,2
100 - 99,7 = 0,2999999999
100 -99,6 = 0,4
100 - 99,5 = 0,5
100 - 99,4 = 0,599999999
100 - 99,3 = 0,7
100 - 99,2= 0,7999999999
100 - 99,1 = 0,9
is this a known issue?
Do you know another calculator where you can review all the line you typed and correct it if needed, that has big buttons, has parenthesis, and that give accurate results? I used to use HiCalc on WinMo, but I can't seem to find a good substitute on android.

Turn the phone to landscape and more functions are available like parentheses. Not sure about your other points!

funny - i needed this calculator for my school time
100 - 99,2= 0,7999999999
i have same result
br stupsi

stupsi99 said:
100 - 99,2= 0,7999999999
Click to expand...
Click to collapse
Google floating point precision

nparley said:
Google floating point precision
Click to expand...
Click to collapse
Most likely this.
And I use RealCalc which seems to correct for it.

This is mad.
My calculated is screwed too. Lol
Sent from my HTC Desire using XDA App

Why are you putting commas in not decimal points? 99.7 not 99,7

^^^^ Other people in the world write things differently to us

ok...this is new...lol
do you guys think a solution is possible? or should we all get another calculator?lol

You need to get another calculator.
Seems that HTC's calculator is using floating point rather than fixed point or decimal floating point.
Regards,
Dave

it is also a problem on the Vanilla calculator.
I'm using OpenDesire and it also has this problem.

bedeabc said:
^^^^ Other people in the world write things differently to us
Click to expand...
Click to collapse
they might, but if the calculator is configured to work with points not commas I'm not surprised it fails
Edit
Wrong! Is the same with points as commas. My bad

When we use the calculator we press the . button, as there is no comma.
FYI when in the UK you write 1,002.50 the rest of the world writes 1 000,50.
HTC answered me to find another calculator on the maket, cause the HTC calculator is a basic one. LMAO I know it won't solve complex equations, but 100 - 99.9 should be solved by any basic calculator, even by a 7 year old pupil...so I guess it should be solved by a calculator that displays basic trigonometry buttons, shouldn't it?

It fails with points as well.
100-99.9=0.0999999999
So it's not a localisation thing, it's just a rubbish calculator.

This happens to any substraction having the following pattern:
n-((n-1)+p), where p = {0.9, 0.7, 0.4, 0.2}
And it doesn't matter whether the Calculator uses '.' or ',' for digits.
Very strange...

Benj555 said:
FYI when in the UK you write 1,002.50 the rest of the world writes 1 000,50.
Click to expand...
Click to collapse
That depends on your definition of the rest of the world.
The two most populous nations on the planet, namely China and India, use the point as the decimal separator, as does the US, Japan, and most of the ex-British empire.
For the most part, the "Decimal Comma" is in use in mainland Europe and most of South America.
Regards,
Dave

Benj555 said:
When we use the calculator we press the . button, as there is no comma.
FYI when in the UK you write 1,002.50 the rest of the world writes 1 000,50.
Click to expand...
Click to collapse
The 'rest of the world' write: 1.000,50 (they use the '.' to group thousands - e.g. 154.234.345,243)

nparley said:
Google floating point precision
Click to expand...
Click to collapse
Don't see why floating point should have anything to do with this. Floating point is relevant where there is a greater number of digits required to do the calculation than would normally be displayed. This is a simple subtraction of a number with one decimal place. This is just plain wrong!

norm2002 said:
Don't see why floating point should have anything to do with this. Floating point is relevant where there is a greater number of digits required to do the calculation than would normally be displayed. This is a simple subtraction of a number with one decimal place. This is just plain wrong!
Click to expand...
Click to collapse
nparley is correct.
Whomever wrote the HTC calc app used binary floating point data types. The subtraction is being performed "correctly" within the limitations imposed by the use of that data type. 0.1 cannot be exactly represented by that data type, which is why this issue shows up.
Regards,
Dave

No, in the UK we would use . to indicate decimal and , to indicate thousands. Which I think is standard?

Copy and Paste "Limitations"

http://blog.walshie.me/2011/01/25/forthcoming-windows-phone-update-the-bits-that-are-real/
This just in.
I don't see a major problem but here's the news for you!

Sad. If I'm reading that right, C&P won't function in the phone app...for...like...copying a phone number from one area (maybe from a browser) to the new contact input fields.
Thank you, MS, for such a ...erm...experience...with WP7

Well, you are reading it wrong. The stuff is about third party applications. It doesn't say anything about native apps, so we don't know how it will function and where.
As regards third party apps, there's nothing wrong with using a control designed for text, for, er, displaying text. That's the way it should be. Not everything should be selectable, and it isn't selectable in all OSes including "big" Windows.

MartyLK said:
Sad. If I'm reading that right, C&P won't function in the phone app...for...like...copying a phone number from one area (maybe from a browser) to the new contact input fields.
Thank you, MS, for such a ...erm...experience...with WP7
Click to expand...
Click to collapse
Well, depending on how the text is set up, you should be able to just tap a phone number in any built-in app and it will bring up the create contact section.

I read from the article that in 3rd party apps you'll be able to c&p only text from text boxes. So you can't copy twitter tweet right from the timeline.
So apparently you'll be able to c&p whatever you want from text boxes,
Plus probably other displayed content from native apps.
So I think not a huge problem here.

FishFaceMcGee said:
Well, depending on how the text is set up, you should be able to just tap a phone number in any built-in app and it will bring up the create contact section.
Click to expand...
Click to collapse
Was just, for the sake of minimizing comment, using that as an example, not as limited to. I'm more concerned with being about take information from emails or text messages or other content in a browser and being able to put it elsewhere when I need to.
I hope nobody is going to try to tell me I never have need for it...sheesh.

MartyLK said:
Was just, for the sake of minimizing comment, using that as an example, not as limited to. I'm more concerned with being about take information from emails or text messages or other content in a browser and being able to put it elsewhere when I need to.
I hope nobody is going to try to tell me I never have need for it...sheesh.
Click to expand...
Click to collapse
I'm fairly sure copy & paste has been shown in places like the web browser, email, and office during the demos. Don't worry so much, this article clearly states 3rd party apps.

PG2G said:
I'm fairly sure copy & paste has been shown in places like the web browser, email, and office during the demos. Don't worry so much, this article clearly states 3rd party apps.
Click to expand...
Click to collapse
Cool. Appreciate the update.

MartyLK said:
I'm more concerned with being about take information from emails or text messages or other content in a browser and being able to put it elsewhere when I need to.
Click to expand...
Click to collapse
Anywhere you can select text, like you can in the browser, should work. Text messages (unless they change it) you would have to go through the motions of choosing Forward from the longpress menu then select the text from the text box; a bit long-winded but doable.

If Microsoft can add the function I would imagine DEVs could also make use of it in their apps. I could be wrong.

Yeah, they're talking about how devs can modify their text fields to utilize the C&P feature when they update their apps.
Hope they actually do this...

Thanks for the post. Been waiting for this.

This, while exactly what I expected after hearing what Mr. Kindel had to say, is a downer. Now, I don't use cut'n'paste that often on phones, but when I do it's almost exclusively from non-edit controls.
I would also have expected a way to copy'n'paste images considering they see Office as such a big thing, and TBH I quite often paste product images into OneNote on the computer - which syncs perfectly to the phone. Of course you're unable to edit the photo note on the phone, but just being able to cut'n'paste them would be great still.
TBQH this looks more like a half-assed implementation done quickly to get an update out the door.

If copy-n-paste is available at API level, there is nothing to stop app developers to implement whatever they like to support the feature directly.
The limitation of text box is only a limitation when the devs are too lazy to re-complile their code.
Of course, if such feature is not available at API level, that will be a true limitation. Personally, without multi-tasking support for 3rd party apps, copy-n-paste usage will still be quite limited.
Without the tradditional stylus and resistive touch screen, try to accurately select the text you want to copy on a capacitive screen using your fingers is nothing but frustration. I tried a few times on my Android phone and never worked for me. A pen and paper is much easier to do than copy-n-paste.

foxbat121 said:
...Without the tradditional stylus and resistive touch screen, try to accurately select the text you want to copy on a capacitive screen using your fingers is nothing but frustration. I tried a few times on my Android phone and never worked for me. A pen and paper is much easier to do than copy-n-paste.
Click to expand...
Click to collapse
Have you tried a WP7 device? I know we can't currently select, but the "cursor" that is implemented at the moment (useful for adding/deleting stuff in texts) is pretty good.

Casey_boy said:
Have you tried a WP7 device? I know we can't currently select, but the "cursor" that is implemented at the moment (useful for adding/deleting stuff in texts) is pretty good.
Click to expand...
Click to collapse
I must say the virtual cursor on WP7 is pretty nicely implemented.
Android sucks compared to this and is a pain sometimes.

I guess you guys haven't tried 2.3 or any new samsung devices. Copy and paste, and the cursor is very finger friendly.

I have used cursor on Android 2.2. It is much better than 2.1 but still copy-n-paste largely dependent on app's implementation.
Capacity touch screens are inheritally inaccurate. Cursors make it less painful to use but can't eliminate that inaccuracy. You just got a tool to let you fine tune your selection. It still takes multiple tries to accomplish the job. And god forbid, if you want to select a paragrah out (multiple lines) of an email, that cursor won't be much help to you.

foxbat121 said:
If copy-n-paste is available at API level, there is nothing to stop app developers to implement whatever they like to support the feature directly.
The limitation of text box is only a limitation when the devs are too lazy to re-complile their code.
Of course, if such feature is not available at API level, that will be a true limitation. Personally, without multi-tasking support for 3rd party apps, copy-n-paste usage will still be quite limited.
Without the tradditional stylus and resistive touch screen, try to accurately select the text you want to copy on a capacitive screen using your fingers is nothing but frustration. I tried a few times on my Android phone and never worked for me. A pen and paper is much easier to do than copy-n-paste.
Click to expand...
Click to collapse
You already could select and hold and image to save it, then go to One Note and insert it.

I remember holding the.control button on WM devices and selecting/copying multiple items. Those were the days.

Barcode scanner, offline (no internet connection needed)

Hi guys.
Who wanted a free barcode scanner? Here we are...
No network connection needed; app based on zxing library and Kevin Marshall's (from Clarity Consulting, can't remember his blog url now) code.
I just slightly modified the original code and added a few (probably useful but not sure ) services.
App interface is very simple: run application, focus on barcode, and wait until code is recognized. Touch handset screen to run recognition again.
Buttons description:
- "Save" saves captured barcode to jpeg;
- "Bing" and "Google" used for barcode web lookup (probably this part needs more work)
- "Mail" and "SMS" used for sending recognized code text.
Enjoy!
UPDATE 1: v 1.1, auto focus added;
UPDATE 2: v 1.2, orientation-less UI added, project moved to opensource at googlecode: http://code.google.com/p/barcodescan/
UPDATE 3: v 1.2.1, slightly changed autofocus logic, now works better on HTC. Download link: http://barcodescan.googlecode.com/files/BarcodeScanner.xap
UPDATE 4: v 1.2.2
- barcode search improved;
- added HTC detection, changes in autofocus logic;
http://barcodescan.googlecode.com/files/BarcodeScanner_1.2.2.xap

Is this a marketplace app?

sensboston said:
Hi guys.
Who wanted a free barcode scanner? Here we are...
No network connection needed; app based on zxing library and Kevin Marshall's (from Clarity Consulting, can't remember his blog url now) code.
I just slightly modified the original code and added a few (probably useful but not sure ) services.
App interface is very simple: run application, focus on barcode, and wait until code is recognized. Touch handset screen to run recognition again.
Buttons description:
- "Save" saves captured barcode to jpeg;
- "Bing" and "Google" used for barcode web lookup (probably this part needs more work)
- "Mail" and "SMS" used for sending recognized code text.
Enjoy!
Click to expand...
Click to collapse
I can't seem to get it to do anything. It says 'Scanning...' and I'm trying different distances to codes, but nothing ever happens. Any pointers?

Is this limited to any country or is it just reading out what the barcode says?

OK, lets go through step by step:
- it's not a marketplace app and have no chance to be published 'cause it uses undocumented camera API; you should download and unpack attachment and sideload the app;
- if you can't capture the barcode, try better lighting. Also, move a handset to autofocus camera. In my tests the scanner captured 100% of barcodes: from books, computer part boxes, foodstuff...
- it's not limited to US 'cause (I believe) the barcodes are international. And yes, it's just reads the barcode; however you may bing or google results, in the most cases search engines able to find product/book description or specifications.
It's a very basic scanner; if someone can recommend online API/service to parse barcode value, I can add it to the program (but I really do not want to spend much time for this)

It technically works but the issue is lack of AF or Macro access.
On my Focus, it only works if I scan a barcode off of my PC (do an image search for one) --then it's super fast and quick.
Books, CDs, etc. do not work, regardless of lighting or distance--I suspect because the camera is not trying to AF. Any work around to that?

I've tested first on HTC Surround - work perfect (I can prove). But you've right about Focus'es bad autofocus (LOL, sound nonsense - "Focus have no autofocus"!).
Will see what I can do... Any other suggestions or wishes (about barcode lookup, UI, etc.)?
P.S. Fixed (reload version from the first post), now working good on Samsung Focus.

sensboston said:
I've tested first on HTC Surround - work perfect (I can prove). But you've right about Focus'es bad autofocus (LOL, sound nonsense - "Focus have no autofocus"!).
Will see what I can do... Any other suggestions or wishes (about barcode lookup, UI, etc.)?
P.S. Fixed (reload version from the first post), now working good on Samsung Focus.
Click to expand...
Click to collapse
Boom.
Working great on Focus now. Nice job. Think I'll try an LG next... bwahaha
As far as changes, no none right now. I'm sure what other apps use for barcode price comparisons--but perhaps a tie into Amazon or eBay would be good. Too bad you can't just jack into ShopSavvy's system with it, lol. If I think of any, will post back.
Edit: Working on LG Quantum too!

sensboston said:
I've tested first on HTC Surround - work perfect (I can prove). But you've right about Focus'es bad autofocus (LOL, sound nonsense - "Focus have no autofocus"!).
Will see what I can do... Any other suggestions or wishes (about barcode lookup, UI, etc.)?
P.S. Fixed (reload version from the first post), now working good on Samsung Focus.
Click to expand...
Click to collapse
hmm, 1.0 wasn't upside down, but 1.1 is upside down on my Focus. Anyone else see this?

davux said:
hmm, 1.0 wasn't upside down, but 1.1 is upside down on my Focus. Anyone else see this?
Click to expand...
Click to collapse
Nope. Fine on my Focus. It does work with accelerometer, you sure that isn't it?

Works well on my HD7! Great job! Hopefully it will tie in with Amazon and save previous searches within the app etc

sensboston said:
Hi guys.
Who wanted a free barcode scanner? Here we are...
No network connection needed; app based on zxing library and Kevin Marshall's (from Clarity Consulting, can't remember his blog url now) code.
Enjoy!
UPDATE: v 1.1, auto focus added;
Click to expand...
Click to collapse
Do you have any interest in releasing the source? I may have some time to improve upon this a bit, but I'd rather not start from scratch (or step on any toes re-creating virtually the same thing).
malatesta said:
Nope. Fine on my Focus. It does work with accelerometer, you sure that isn't it?
Click to expand...
Click to collapse
Good call, I was holding it strangely every time I opened it before. It works great.

davux said:
Do you have any interest in releasing the source? I may have some time to improve upon this a bit, but I'd rather not start from scratch (or step on any toes re-creating virtually the same thing).
Click to expand...
Click to collapse
Why not? I'm really do not have time for that project...
Here we are: http://code.google.com/p/barcodescan/
Send me a PM with your gmail and I'll add you to the project contributors. Do not forget comment each commit, increment solution version and promptly build community release (and upload xap to the project's download page!) - and you allset
BTW, there are many things to improve: better UI (completely orientation-less), additional functionality - commit found barcodes to database etc. etc. etc.

Please review and follow these rules, it appears you aren't following them, you most likely aren't following the template. So fix it quick . It is not a harsh criticism, it is just for consistency and better for the user. PM me for help or support!
If this post is here and your thread is closed, it means that you aren't following them and your intentions are for gain only.​
~~Tito~~

problem htc hd7
how do i copy this scanner programme to my htc hd7
i really hate this phone i had a htc touch pro 2 and it was far better can someone help me out here and also if some one can teach me how to customize personal ringtone would be great

Thx for the code. Really usefull to learn from this
Sometimes when you scan a barcode and touch the screen to start again. After a few seconds it stops and shows the last barcode again.
It looks like the UI thread is catching up scanning some images. How to get rid of this?

ajhvdb said:
It looks like the UI thread is catching up scanning some images. How to get rid of this?
Click to expand...
Click to collapse
Sorry, I don't have a time for that application now but it should be significantly refactored.If you want you may join the project and continue development, we can share some ideas for app improvement etc.
As for problem u described, you should play with the different capture resolutions or give some hardcoded "pause" to recognition library Also, MS camera API (still not officially allowed) is not documented and very poor... However it's a great field for experiments and hacks

Thanks! That works great on my HD7.

~~Tito~~ said:
Please review and follow these rules, it appears you aren't following them, you most likely aren't following the template. So fix it quick . It is not a harsh criticism, it is just for consistency and better for the user. PM me for help or support!
If this post is here and your thread is closed, it means that you aren't following them and your intentions are for gain only.​
~~Tito~~
Click to expand...
Click to collapse
Please follow up on this!

sensboston said:
Sorry, I don't have a time for that application now but it should be significantly refactored.
Click to expand...
Click to collapse
Im not that experienced in multiple threads. Do you think the problem is in the Zxing lib?
Looking at the code the Zxing lib should have a completed event from which you can restart or show the image.
This code works but is racing and racing in the UI thread and after finding a barcode and restarting it looks like something from a buffer is used..
Code:
private void GrabFrame()
{
Dispatcher.BeginInvoke(() =>
{
if (_Camera != null && CameraVisualizer.Visibility == Visibility.Visible)
{
WriteableBitmap wb = new WriteableBitmap(640, 480);
_Camera.GetCurrentFrame(wb);
wb.Invalidate();
ScanBarcode(wb);
wb.DisposeIfPossible();
GrabFrame();
}
});
}