Paul,
Passed this along to some people. One of which I hope reaches out to
you. He's officially retired now but might be bored enough for something
small like this. He's had a rather high success rate debugging into Qt
source and fixing things for embedded projects.
Send private email if you are looking to cast a wider net than just
people we know. I do know of one low level (firmware and embedded
systems) that I've worked through many times. They just might have
someone. Always seem to have the person with odd/niche skills in this
world. Not going to expose you to that without you asking though.
Hopefully you get the response you need from this post. Best of luck
getting the fix rolled into base line code.
On 2/16/19 4:00 AM, interest-requ...@qt-project.org wrote:
Message: 12
Date: Fri, 15 Feb 2019 15:24:06 -0500
From: Paul Knopf<pauldotkn...@gmail.com>
To:interest@qt-project.org
Subject: [Interest] Work for hire to solve a Qt bug that's been a
thorn in our side.
Message-ID:
<cakmwj-3ivac89z+xc3ujgbhz4obhwcce14ubhzwjdvi2rme...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Are there any experienced Qt developers out there interested in solving
this bug that my company is experiencing? Maybe you know someone who is
interested?
https://bugreports.qt.io/browse/QTBUG-73830
It is easy to reproduce with any Qt version, on Linux.
Thanks for your attention/help.
--
Roland Hughes, President
Logikal Solutions
(630)-205-1593 (cell)
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
