I also compiled sensor_explorer from the example code, it also cause segment
fault on real device.
Is there any other ways to get sensor capabilities?
I am using MeeGo 1.1, is it the reason? Will it work on MeeGo 1.2?
B.R.
He Yunlong
From: Zhao, Forrest
Sent: Wednesday, May 11, 2011 1:06 PM
To
Hi,
Please find attached two patches for QtContacts EDS backend:
0001: Make the QContactAbstractRequest::start() method return a boolean so that
the caller knows when an error occurred and the request could not be started.
0002: Make the QContactFetchRequest and QContactLocalIdFetchRequest really
Did you ever look into qtmobility-examples? You can find the proper usage of
sensor API.
If you’re sure that you use the API in correct way, please file a bug at
bugs.meego.com and attach your program to reproduce the bug.
Thanks,
Forrest
From: meego-dev-boun...@meego.com [mailto:meego-dev-bou
Hi, Experts,
I am trying to get sensor types supported by one device, so I tried to use
QSensorManager::createBackend ( QSensor * sensor ), however, it cause
application segment fault with QOrientationSensor, do you know whether this is
a bug? Or is there other ways to get supported sensor li
On May 10, 2011, at 1:16 PM, Attila Csipa wrote:
> On Monday 09 May 2011 18:22:17 you wrote:
>>> This has been discussed - and agreed before - but the changes never
>>> seemed to happen :-(
>>
>> The suggestion to rename the mailing lists was discussed but never
>> agreed to. I, for one, don't b
On Monday 09 May 2011 18:22:17 you wrote:
> > This has been discussed - and agreed before - but the changes never
> > seemed to happen :-(
>
> The suggestion to rename the mailing lists was discussed but never
> agreed to. I, for one, don't believe that renaming the list will solve the
Just out o
thats looks good to me, I will take a closer look and see how it can be
integrated.
Anas
On 21 Jan 2011, at 20:06, Carsten Munk wrote:
> 2011/1/19 Carsten Munk :
>> Hi,
>>
>> One of the biggest problems about debugging on mobile devices running
>> MeeGo is that our debuginfo packages currently
On Di, 2011-05-10 at 08:40 +0100, Dumez, Christophe wrote:
> Please find attached a few patches for QtContacts EDS backend:
> 0001: Make the contact save/remove requests really asynchronous. This
> should increase performance because the async requests can now
> actually run in parallel instead of
Agenda for the Dialer Project meeting - Tuesday, May 10th, 2011
* General information/business (Shane)
- QML Dialer status (Shane/Tom)
* Which dialer in N900 DE image for MeeGo SF2011? (DE Team rep.)
* Bug, patch and merge-request status (Shane)
On 5/10/2011 2:16 AM, Murray Cumming wrote:
I hope to see some official acceptance for Maalit in Meego 1.3. After
all, it's gotta have a serious input method framework. The libmeegotouch
dependency seems to be the only problem so far. But you need to be loud,
clear and direct to Nokia that they
On Tuesday, 10 de May de 2011 10:42:06 Michael Hasselmann wrote:
> On Tue, 2011-05-10 at 11:29 +0300, Sakari Poussa wrote:
> > That (Qt5) is a vision with timeline. It's not 10 years, it is 1+ year
> > as you can read from the blog.
> >
> > These are big and complex things which need long cycles t
On Tue, 2011-05-10 at 11:16 +0200, Murray Cumming wrote:
> On Tue, 2011-05-10 at 01:45 -0700, Arjan van de Ven wrote:
> > regardless of that, for MeeGo libmeegotouch is not our preferred way
> > of
> > writing applications, or even a supported one.
> > so cleaning that up is a target anyw
On Tue, 2011-05-10 at 01:45 -0700, Arjan van de Ven wrote:
> regardless of that, for MeeGo libmeegotouch is not our preferred way
> of
> writing applications, or even a supported one.
> so cleaning that up is a target anyway.
As Meego 1.3 is planned for 6 months from now, that doesn't se
On 5/10/2011 1:42 AM, Michael Hasselmann wrote:
On Tue, 2011-05-10 at 11:29 +0300, Sakari Poussa wrote:
That (Qt5) is a vision with timeline. It's not 10 years, it is 1+ year as you
can read from the blog.
These are big and complex things which need long cycles to be planned and
communicated
On Tuesday, 10 de May de 2011 11:29:09 Sakari Poussa wrote:
> > "In future version*s*" could be 10 years from now, for all we know
> > (given it took 5 years from Qt 4 to Qt 5 already, the latter not being
> > there yet). You really think you need to prepare for that right now?
>
> That (Qt5) is a
On Tue, 2011-05-10 at 11:29 +0300, Sakari Poussa wrote:
> That (Qt5) is a vision with timeline. It's not 10 years, it is 1+ year as you
> can read from the blog.
>
> These are big and complex things which need long cycles to be planned and
> communicated correctly. That's what we (MeeGo) are doi
On May 9, 2011, at 4:01 PM, Michael Hasselmann wrote:
> On Mon, 2011-05-09 at 14:49 +0200, Carsten Munk wrote:
As we know, in the future Qt versions the QtGraphicsView will be
deprecated in the favor of SceneGraph.
>>>
>>> Never heard of this. AFAIK, the scene graph doesn't even exist
On May 9, 2011, at 3:49 PM, Carsten Munk wrote:
> 2011/5/9 Alberto Mardegan :
>> Hi,
>>
>> On 05/09/2011 01:23 PM, Sakari Poussa wrote:
>> [...]
>>>
>>> As we know, in the future Qt versions the QtGraphicsView will be
>>> deprecated in the favor of SceneGraph.
>>
>> Never heard of this. AFAIK,
18 matches
Mail list logo
