Notices

So no great news yet, but the PythonQt and DBus plugins compile and install and are loaded by mBarcode, but they don't currently receive any signals from the rest of the plugin arch (i.e. no qDebug() output from their barcodeAnalysed() callbacks).

If anyone's bored and fancies doing some debugging then the more the merrier!

I also see that Dragly (I don't remember doing it myself anyway!) very kindly moved the vCard import code to use the QtMobility functions, which means it should now be reasonably trivial to construct a contact object by parsing the mecard contents. Again if anyone fancies doing some work on that, that would be good, otherwise I'll sort it out once I've got these wrapper plugins working properly.

Ah, I've realised why the plugin sinks don't receive anything, I'd based my code on the old plugin structure and ignored the (relatively) new stuff such as QSet<PluginAction*> Plugin::getPluginActions().

I'll sort that out this evening.

Any hope you will fix the mbarcode version that is currently in the Extras*? It hangs for a very loong while, without reporting any progress, when trying to use plugins (web search plugin, actually).

Once I've got these extra plugins sorted I'll push an update to Extras-*, sorry for the delay.

I've just looked and websearch plugin seems to work in its current form (0.1.15-1, which hasn't been changed since August afaict), what version are we talking about here and what's the problem?

Edit: looks like this is the version currently in Extras-devel too: http://repository.maemo.org/extras-d...in-webrequest/

OTOH, the mBarcode UI appears un-responsive while the Hildon conic (is that the name, I forget) web connection popup is being prepared, which we should probably fix.

In fact the buttons appear unresponsive full stop, nothing to do with the libconic stuff. I need to tap each twice quickly to get it to respond. I'm trying to find out what's up with that now.

As I've been bust writing plugins rather than using existing ones I've not noticed this. Sorry!

Right, I've fixed the un-responsiveness, firstly by only looking for plugins that were slow to respond ever 1000ms, and secondly by only re-creating the plugin button list if a new plugin is found.

I have noticed though that the list uses custom delegates and these don't have any way to show they have been pressed. I need to do some reading to work out what I should do in ResultsWindow:n_tblResults_clicked(QModelIndex index) to re-paint this list item with some extra colour added. Any thoughts/ideas appreciated.

I'll push an update to extras-devel this evening come what may, though I want to reduce the start up delay by moving the gst pipeline setup to a thread before we push this to extras-testing.

Yes, yes, yessss!

As I have had -Devel permanently enabled for months now, this is not a problem, personally.

Ok, I've just pushed a new version of mBarcode (for Fremantle) to the extras-devel builder. The plugins are all the same, but the main program should be a bit more responsive, and also allows you to select either continuous scanning (with half shutter to focus if you don't want continuous focus, and full shutter to record an image) or scan when the shutter is pressed (for iirc 3s after the shutter is pressed, half-press does focus, to save an image use the on-screen button)

I've not managed to get the results window to let you know which button you've pressed, I'll look at this (and if anyone knows about custom delegates for QListViews please pipe up) nor have I worked out why the PythonQt and ExternalDBus wrapper plugins aren't receiving events yet.

I'll look at all of these, but just no more tonight!

Please let me know if there are any issues with the new version of mBarcode.

This is yet another great app for the n900. I've been using it for a few months now and it keeps getting better and better and I want to say thanks... THANK YOU!

Right you asked for feedback and I'll provide. Yes it does startup quicker. It does feel smoother and the scan on request feature is great. There is one slight issue with the new build though. On startup the display gives a high fps reading (~70fps) until one opens the camera shutter. Now I don't open the shutter first because that loads the camera app, and sometimes it's a while before I actually use the app after starting it. I use this app in conjunction with PresenceVNC so I can copy the barcode into a proprietory Windows application. Sometimes the program needs to be started up and logged into. And sometimes a customer comes into the shop and I have to put the phone down and serve them, all before realising that I've not opened the shutter. So you can understand my concern.

One more thing if I may, can you enable the scan to be activated by the spacebar? I tend to use the app with the keyboard open and it's not that easy using the shutter button with the screen up.

This is still a fantastic app even with the little issues.

Thanks again,

mrsellout