On Monday 30 September 2013 13:09:53 Thiago Macieira wrote: > On segunda-feira, 30 de setembro de 2013 19:39:53, Knoll Lars wrote: > > >As far as I know from my colleague, it misses some necessary API -- at > > >least the connection state changes notification and device disappearing > > >notification. > > >We could prepare some patches during the next week or two, though > > >QtBluetooth probably needs few more revisions and API changes/fixes...but > > >we can't do too much in case of API freeze, you know... > > > > A missing feature is for me not enough reason to delay the release of a > > module. There's always more features we could add to a module. It's also > > important to get something out and into the hands of people. > > > > Feature freeze doesn't imply a full API freeze. We have the alpha/beta > > period exactly for finding issues and fixing them. A missing signal is > > something we can fix if required. > > Right. > > However, if there are major defects in the API, they need to be voiced now. > Like Lars said before, this API isn't new, so people have had the time to > look at it. > > If there are major problems, I expect that they are already known. > Therefore, post them.
After having worked quite a bit with the Bluetooth API I wouldn't say it has major defects any more. This wasn't the case with NFC last time I worked with. But afaik there were some change lately addressing the things I found troublesome. Br, Michael _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
