There are several reasons we didn’t include QtGamepad in Qt 6 so far: - does it have enough users to justify the work to keep it alive? - is the design/architecture up to modern Qt 6 standards? - are there things we want to do to support a broader use case? - does anyone want to maintain it?
I have not investigated any of these questions in detail, but I think the answer to question #1 so far has been “no”, and with a life-time history of 33 JIRA tickets for that component that seems sensible. So, instead of moving something with unclear relevance back into the monolithic Qt 6 machinery with its synced-up release machinery, perhaps we can rather explore how a module like this can be developed and made available outside of all that? It seems quite trivial to build this module locally from git, perhaps that’s a sensible starting point for the time being. Volker > On 12 May 2025, at 12:43, Andy Nichols via Development > <development@qt-project.org> wrote: > > Hi Arno, > > Indeed if you pull the latest from qt/qtgamepad from gerrit (dev) it should > work with 6.10 (dev). Also I guess technically it still would be possible to > have it officially in 6.10+, but the module freeze is on Friday of this week > if the wiki is up to date. I’m also not entirely sure what the process is > for adding a new module to Qt (or in this case re-adding). > > If someone could chime in the practicalities of doing this (or a > rebuttal/refusal) I could help get this ball rolling again. > > Regards, > Andy Nichols > From: Arno Rehn <a.r...@menlosystems.com> > Date: Monday, 12 May 2025 at 12:28 > To: Andy Nichols <andy.nich...@qt.io>, Liang Qi <cavendish...@gmail.com> > Cc: development@qt-project.org <development@qt-project.org> > Subject: Re: [Development] Resurrecting QtGamepad > Hi Andy, > > On 12.05.2025 12:19, Andy Nichols wrote: > > I’m a bit confused about what’s being proposed/discussed here. We did > > revive QtGamepad, in so far as we integrated the changes I proposed a > > couple of years ago. That includes a module for recreating 95% of the > > same API that was in QtGamepad in Qt 5.x, as well as many additional > > features that have been requested during the lifetime of QtGamepad > > (support for all joystick-like controllers with a lower level API > > exposing buttons and axis’s etc). > > I guess we're equally confused :-) I was under the impression that the > "new", revived QtGamepad was still in development and not yet > functional. If that it is not the case, all the better! > > > However, the QtGamepad module is not > > part of Qt 6, so it doesn’t have access to the CI infrastructure so it > > can and does break. I’m not sure what is being proposed then. Why not > > just propose that the QtGamepad module be again included in qt5.git > > (qt6) and re-added to the CI/packaging infrastructure? > > So that is if we’re considering giving official status to a “legacy” > > port of the 5.15 version, I would rather us opt for just re-elevating > > qtgamepad as it stands in the official repo now and preparing that one > > for release as part of Qt 6. > > If it works, yes! I'm all for it! > > Cheers, > Arno > > -- > Arno Rehn > Principal Software Engineer > Tel +49 89 189 166 0 > Fax +49 89 189 166 111 > a.r...@menlosystems.com > http://www.menlosystems.com/ > > Menlo Systems GmbH > Bunsenstrasse 5, D-82152 Martinsried, Germany > Amtsgericht München HRB 138145 > Geschäftsführung: Dr. Michael Mei, Dr. Ronald Holzwarth > USt.-IdNr. DE217772017, St.-Nr. 14316170324 > -- > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
