Notices

One could hope the encoder developers were thinking the same thing, but when I researched this I found several online encoders using completely different character sets. I don't remember which it was, but there was even one webpage decoding it's own codes with the wrong char encoding :-p

Letting the user choose an encoding manually should hopefully help us out in the cases where everything else fails.

I have no idea why the visual indication of clicking a button in the results list has disappeared, but I'll look into it ASAP. I think I'll do some work on mBarcode by the end of the week.

Oh dear!

Sounds good, we'll have to think how to implement this in the UI.

Great news!

The list doesn't contain any widgets and uses a custom delegate painter to draw the items, so I imagine the painter will need to be told the location of the selected item so that it can draw e.g. a different background. I don't really know, I got bogged down in the delegate stuff over the past few days and decided to move onto more productive avenues instead.

I'm thinking of moving things like the DBus setup into the same thread that does plugin loading (if possible) just to try to remove as much stuff as possible before the UI is shown. Might also move the gst pipeline setup, but was planning on leaving that for the time being as it will probably necessitate changing how the UI starts up.

I'm also going to split up the qrcode sink into multiple sinks so that for any given payload (e.g. a vCard) it can display separate buttons (i.e. sinks) for both the overall vCard and also the contents. I.e. button to save the vCard, button to dial telephone #s, open URLs, send emails to email addresses, etc.

Oh yes, and get the MECARD reading working as you kindly moved the vCard import to using the QtMobility functions, thanks!

http://chart.apis.google.com/chart?c...%A9my+Hubscher

This has the BOM encoded at the start to indicate it's UTF-8, which seems to decode properly.


On a completely different note, has anyone else found that you sometimes revert back to continuous scanning until you open the Settings dialog? I thought I'd fixed this but apparently not. Drat! - seems to happen to me after I've scanned something. I'll have to check and see what's going wrong there

Yeah I just noticed that today. I'll update to the new version in a minute. Thanks for that.

Ok, fixed the one with the continuing scanning - I think it's because the timed scanning timer is still running if you close the results window quickly after it's got something. I've made it stop when any window is opened now.

I may have also fixed the OpenGLES framerate thing. With the shutter closed at startup I see it start at ~8fps and drop down to 2.5fps or thereabouts. Is that what we're after?

I'm pushing a new version now.

Edit: I should also add that in my efficiency drive, I've paused the pipeline whenever a window is opened. We might need to revisit switching timers off when the app is backgrounded as I have a feeling they remain running.

what happened to mbarcode ? i update it twice till now and it can't detect the firefox barcodes ? before the 2 updates it was perfect but the new updates just messed it up really bad !!!

Really?! Can you give me an example URL with one of these and I'll work out what's up?

Nothing has changed with the decoders, just with the UI and handler code, so it really ought to work as before.

well, earlier i wanted to open a mediafire page which i did many times in the old mbarcode and the camera keeps focusing and flashing infront of the barcode but can't read it or display the URL and now i just tested it in this thread and still the same problem

But can you give us an example of a code which isn't working (i.e. a picture - perhaps taken using mBarcode itself...)? Otherwise it's a bit hard to work out what's wrong.

Quick reply...

The latest version of mbarcode:

First scanned QR code - all correct, Open URL from QR code plugin.

After returning from results page to camera, locking and unlocking the device, scanning a EAN-13 code, the result page contains the old result from QR code ("open URL"), and it can still open URL of the previously scanned QR code.

It's supposedly problem of interaction between the new version of mbarcode and the unchanged QR code plugin, because the problem wasn't noticed in previous versions of mbarcode (or, maybe, such sequence of events hasn't happened before?).

Thank you for mbarcode! I'm using it in manual mode (no auto-focus, no auto-scan).