Frank Osterfeld schreef op 5-11-2013 17:41:
> On Nov 5, 2013, at 5:12 PM, Tony Van Eerd wrote:
>
>> Most of BlackBerry's APIs are async.
>> We are looking at moving some of these APIs into Qt.
>> Just as one example, WiFi Direct.
>>
>> I have been attempting to come up with some solid guidelines o
t@qt-project.org
Subject: Re: [Development] async operation error guidance
> >
> > It could also fail later, as it is mostly asynchronous. Or it could
> succeed with a result. ie
> >
> > Q_SIGNAL void deviceConntected(SomeDevice device);
> > Q_SIGNAL void deviceC
> >
> > It could also fail later, as it is mostly asynchronous. Or it could
> succeed with a result. ie
> >
> > Q_SIGNAL void deviceConntected(SomeDevice device);
> > Q_SIGNAL void deviceConnectionFailed(SomeOtherConnectError
> error);
> >
> > or one signal:
> >
> > Q_SIGNAL void device
On Nov 5, 2013, at 5:12 PM, Tony Van Eerd wrote:
> Most of BlackBerry's APIs are async.
> We are looking at moving some of these APIs into Qt.
> Just as one example, WiFi Direct.
>
> I have been attempting to come up with some solid guidelines of how to deal
> with errors on async operations.
Most of BlackBerry's APIs are async.
We are looking at moving some of these APIs into Qt.
Just as one example, WiFi Direct.
I have been attempting to come up with some solid guidelines of how to deal
with errors on async operations.
Some things to consider:
- the initial request may fail. ie
