Re: Starting a 3G traffic monitoring application for N900: some questions

ally. > > the internal data counter uses dbus maybe and I think it's better > to use dbus at this point thab trying to query internal datacounter. > Please take a look at gconf: /system/osso/connectivity/network_type/GPRS keys "gprs_tx_bytes" and "gprs_rx_bytes"

Missing dependencies in extras devel

Hi, I sent a new version of call forwarding applet to extras devel builder, and now it has some missing dependencies even though these hasn't been any changes since previous version: http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/callforwarding/0.4/ Does extr

Re: Pin Code / Lock dialog.

Have you checked API provided by libcodelockui1-dev package? -Mikko Lähettäjä: maemo-developers-boun...@maemo.org [maemo-developers-boun...@maemo.org] käyttäjän Petite Escalope [miniscal...@gmail.com] puolesta Lähetetty: 24. joulukuuta 2009 3:36 Vastaanot

Download request signal in browser-eal

Hello all, I have an application which has an internal web browser. It is a WEB Engine widget from browser-eal. In Chinook everything worked nicely, but now when I updated to Diablo download request signals aren't working anymore. I have connected it: g_signal_connect(en_notify, G_WEBWIDGET_SIG

RE: How to know target in makefile?

PROTECTED] Sent: 17. kesäkuuta 2008 13:39 To: Mikko Mehtonen Cc: maemo-developers@maemo.org Subject: Re: How to know target in makefile? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mikko Mehtonen wrote: > Is there a way to know in Makefile which target we are building (arm > or x86)?

How to know target in makefile?

Hi, Is there a way to know in Makefile which target we are building (arm or x86)? There seems to be a variable $target in scratchbox, but it isn't exported so it's not visible in Makefile. Mikko ___ maemo-developers mailing list maemo-developers@maem