On Wed, 2011-03-23 at 10:31 +0200, Kimmo Hämäläinen wrote:
On 03/23/11 00:30, ext Tarantism wrote:
I'd like to disable the system touch screen click for my application.
The best way depends on your application. Do you use GTK/Qt/pure-X or what?
I'm using Qt.
In GTK, you could create
I'd like to disable the system touch screen click for my application.
Can this be done?
Thanks.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
On Wed, 2011-02-09 at 10:28 +0100, Henning Heinold wrote:
you could use dbus-monitor to examine what dbus-send is sending
and what is the result out of the qdbuxml thinigie is. Maybee
the tool does something wrong.
Thanks for the suggestion. dbus-monitor doesn't show any activity from
the
I'm trying to check the system volume from a Qt C++ application. I saw
that I could set (and found that I could read) volume over dbus talking
to com.nokia.mafw.renderer.Mafw-Gst-Renderer-Plugin.gstrenderer
This works fine using dbus-send but when I follow the instructions to
use qdbusxml2cpp, I
I'm trying to install ESBox for Eclipse but can't get a response from
http://maemoide.nokia.com/updates/2.0/esbox
Is the link out of date or is the server down?
___
maemo-developers mailing list
maemo-developers@maemo.org
On Mon, 2010-08-23 at 16:54 +0200, Marc-André Lureau wrote:
Hi
The only way that really works well, whatever autotools you have in
scratchbox, is to run autogen.sh/bootstrap.sh (with NOCONFIGURE=1)
outside of scratchbox, and then build the rest in scratchbox.
I understand that can make
After many hours in autotool hell, I've finally managed to build
pulse-0.9.15 (from here
http://repository.maemo.org/pool/fremantle/free/p/pulseaudio/pulseaudio_0.9.15-1maemo38+0m5.tar.gz)
for the N900 in scratchbox using the supplied:
./bootstrap.sh make make install
I'm particularly
On Sun, 2010-08-22 at 18:33 +0100, tarantism wrote:
After many hours in autotool hell, ... blah blah ...
... more blah
Am I missing something in the build procedure?
No. Just a badly 'installed' libtool upgrade to 2.2. I had the binary on
the path but not the lib and include files.
I have found
