On Sun, Sep 9, 2012 at 4:41 AM, Rene Jensen wrote:
>
> You got my attention enough that I wanted to look into it (although I'm
> totally *not* worthy of even attempting to fix stuff in Qt, nor do I have
> the time for it). I am pretty close to the scenario above. Fresh Win7, just
> installed the d
On 10 September 2012 19:20, Ariel Molina wrote:
>> I grabbed the Intuos 3, it's still around. And I can reproduce the
>> bug that with Qt 4.x apps (even the latest Creator released) it's not
>> usually possible to interact with most QWidgets using the Wacom mouse.
>
> Are you able to reproduce th
> On 10 September 2012 12:58, Shaw Andy wrote:
>
> > To clarify, I did the patch that everyone is referring to, I actually did
> > it in my
> Nokia days when I had access to the tablet and passed it on to someone after
> I joined Digia. It is a hack because I had to try and get around the mous
> I grabbed the Intuos 3, it's still around. And I can reproduce the
> bug that with Qt 4.x apps (even the latest Creator released) it's not
> usually possible to interact with most QWidgets using the Wacom mouse.
Are you able to reproduce the bug i originally found?
1. Unplug your wacom
2. Grab
On 10 September 2012 12:58, Shaw Andy wrote:
> To clarify, I did the patch that everyone is referring to, I actually did it
> in my Nokia days when I had access to the tablet and passed it on to someone
> after I joined Digia. It is a hack because I had to try and get around the
> mouse posit
Op 10-9-2012 15:45, Boudewijn Rempt schreef:
> I mean, there clearly are more important users of Wacom support in Qt than me
> with Krita.
Don't underestimate yourself ;-)
André
___
Development mailing list
Development@qt-project.org
http://lists.qt-pro
On Monday 10 September 2012 Sep, Shaw Andy wrote:
> > On domingo, 9 de setembro de 2012 13.25.29, Boudewijn Rempt wrote:
> > > The solution for a bug can never be to wilfully break existing
> > > applications!
> > > What can I as an application developer depend on if that's deemed
> > > acceptable
> On domingo, 9 de setembro de 2012 13.25.29, Boudewijn Rempt wrote:
> > The solution for a bug can never be to wilfully break existing applications!
> > What can I as an application developer depend on if that's deemed
> > acceptable? "Yeah, we had a feature, and yeah, people depend on it, but
> w
On domingo, 9 de setembro de 2012 13.25.29, Boudewijn Rempt wrote:
> The solution for a bug can never be to wilfully break existing applications!
> What can I as an application developer depend on if that's deemed
> acceptable? "Yeah, we had a feature, and yeah, people depend on it, but we
> don't
On Sunday 09 September 2012 Sep, Thiago Macieira wrote:
> On domingo, 9 de setembro de 2012 11.46.31, Boudewijn Rempt wrote:
> > > Preferably, it should be fixing it once and for all.
> >
> > Well, given that Digia actually seems to have a patch for the bug in
> > question, I'd say that the choice
On domingo, 9 de setembro de 2012 11.39.36, Frank Hemer wrote:
> On Sunday 09 September 2012 11:19:41 Thiago Macieira wrote:
> > What were you referring to when you said "you cannot be serious about
> > that"?
> I refer to the very last part of your statement, citing: 'So there's nothing
> we need
On domingo, 9 de setembro de 2012 11.46.31, Boudewijn Rempt wrote:
> > Preferably, it should be fixing it once and for all.
>
> Well, given that Digia actually seems to have a patch for the bug in
> question, I'd say that the choice is easy. Use the bug fix. If Qt goes
> down the way of "it's bette
On Sun, 9 Sep 2012, Thiago Macieira wrote:
> On domingo, 9 de setembro de 2012 10.55.10, Frank Hemer wrote:
>>> Note that this also applies for Qt 4.8. If the support is broken there and
>>> causing issues like Ariel is describing, it's definitely a P1 that needs
>>> fixing. If we can't muster the
> That combination of items just doesn't make sense to me.
> Your scenario might differ, but try this: a clean Win7 HP or Pro
> install, get any of the latest Intuos4 driver, Qt 4.8.x (I used the
> SDK) and QtC 2.5.x, create a new QtQuick UI, just the simple "Hello
> World" QtC creates for you. Swi
On Sunday 09 September 2012 11:19:41 Thiago Macieira wrote:
> On domingo, 9 de setembro de 2012 10.55.10, Frank Hemer wrote:
> > > Note that this also applies for Qt 4.8. If the support is broken there
> > > and
> > > causing issues like Ariel is describing, it's definitely a P1 that needs
> > > fi
On domingo, 9 de setembro de 2012 10.55.10, Frank Hemer wrote:
> > Note that this also applies for Qt 4.8. If the support is broken there and
> > causing issues like Ariel is describing, it's definitely a P1 that needs
> > fixing. If we can't muster the knowledge of how to fix it properly, we
> > s
On Sunday 09 September 2012 09:25:20 Thiago Macieira wrote:
> On sábado, 8 de setembro de 2012 21.25.21, Ariel Molina R. wrote:
> > > 3. So, you propose to remove tablet support in Qt 5.
> >
> > I proposed on the IRC channel two options and a third one appeared:
> > 1) Qt::WA_AcceptWacom flag, to
On sábado, 8 de setembro de 2012 21.25.21, Ariel Molina R. wrote:
> > 3. So, you propose to remove tablet support in Qt 5.
>
> I proposed on the IRC channel two options and a third one appeared:
> 1) Qt::WA_AcceptWacom flag, to be used explicitly to get wacom events
> 2) --enable-wacom on the comma
> 1. Qt 4's wacom tablet on Windows gives you trouble, because you have artists
> who use a wacom puck in a non-standard mode.
No, i have developers working some days on Qt, Quick, using QtC these
days wacoms are kept on a locker, they dont even know how to use them
or care about. *Other* days of
On Saturday 08 September 2012 Sep, Ariel Molina wrote:
> > Feel free to scratch the code if the itch is bugging you!
> This is the point, in a couple of years, few people are being
> scraching *that* code, that's the reason of the state of the code.
> Many users will never find the bug, 'cause the
On Sat, Sep 8, 2012 at 5:10 PM, Ariel Molina wrote:
> > What do you mean by "qmlpuppet"?
> is the pupeteer that enables the QtC Quick designer.
>
I am sorry for putting it this way, but QtCreator is not a good enough
reason to remove this from Qt as said before.
> > As Boudewijn said, it is no
> What do you mean by "qmlpuppet"?
is the pupeteer that enables the QtC Quick designer.
> As Boudewijn said, it is not so costy to get a device. I hope Digia or
> someone else can stand up to get this supported officially for those
> situations where it does not work.
We all know, but none wants t
> Feel free to scratch the code if the itch is bugging you!
This is the point, in a couple of years, few people are being
scraching *that* code, that's the reason of the state of the code.
Many users will never find the bug, 'cause the do not own, or share a
computer with a Wacom tablet. So this bu
On Thursday 06 September 2012 09:03:56 Thiago Macieira wrote:
> On quinta-feira, 6 de setembro de 2012 08.53.11, Boudewijn Rempt wrote:
> > > Another point to consider:
> > >
> > > 1) Quick 2.0 is the way to go, but it targets designers
> > > 2) Designers use mostly Adobe suite and other similar t
On 9/6/12 8:48 AM, "ext Boudewijn Rempt" wrote:
>On Thursday 06 September 2012 Sep, marius.storm-ol...@nokia.com wrote:
>> We only had one guy working on it, and he was primarily on OSX. He
>>hadn't work for us for years now, hence why these bugs have been piling
>>up.
>>
>> I think it shouldn't
On 6 September 2012 08:48, Boudewijn Rempt wrote:
> On Thursday 06 September 2012 Sep, marius.storm-ol...@nokia.com wrote:
>> We only had one guy working on it, and he was primarily on OSX. He hadn't
>> work for us for years now, hence why these bugs have been piling up.
>>
>> I think it shouldn'
>
> 0) It's not a driver issue
> 1) Wacom support is broken in Qt, several bugs are closely related
> 2) QtCreator, qmlpuppet and every single Qt App is affected by bugs right
> now
>
What do you mean by "qmlpuppet"? We have had a commercial QML application
based on Qt 4.8 up and running fine on a
About the state of QTabletEvent in Qt 5: For platforms other than xcb this
event will never be delivered. To be on par with Qt 4 somebody needs to
step up and add support for Windows and OS X. The support on QPA level is
there in QWindowSystemInterface, now it's up to the platform plugins to do
som
On quinta-feira, 6 de setembro de 2012 09.41.28, Boudewijn Rempt wrote:
> Right, so it will be useless, then. Code will compile, but the application
> will be broken and porting to Qt5 will become a really difficult task.
Just as difficult as porting with an incomplete and broken support.
--
Thia
Op 6-9-2012 9:41, Boudewijn Rempt schreef:
> For me as an application developer, I wonder what the alternative
> would be. I guess to write two platform specific event handlers myself
> (win and X11, I cannot afford a Mac) and synthesize the
> QTabletEvents... Do a fund raiser to get me some dif
On Thursday 06 September 2012 Sep, Thiago Macieira wrote:
> On quinta-feira, 6 de setembro de 2012 09.13.01, Boudewijn Rempt wrote:
> > > But since I made the suggestion to remove it: if we can't get it tested
> > > and get it to work, just disable the support. No code needs to be
> > > removed. J
On quinta-feira, 6 de setembro de 2012 09.13.01, Boudewijn Rempt wrote:
> > But since I made the suggestion to remove it: if we can't get it tested
> > and get it to work, just disable the support. No code needs to be
> > removed. Just make the loading of the Wacom DLL always fail.
>
> So, basical
On Thursday 06 September 2012 Sep, Thiago Macieira wrote:
> He's saying that Qt Creator and those other applications don't work on those
> workstations that have Wacom tablets installed. You know very well that
> working for you is no guarantee that it works for everyone.
And the converse is tr
On quinta-feira, 6 de setembro de 2012 08.53.11, Boudewijn Rempt wrote:
> > Another point to consider:
> >
> > 1) Quick 2.0 is the way to go, but it targets designers
> > 2) Designers use mostly Adobe suite and other similar tools
> >
> > (this means probably Wacoms in there)
> >
> > 3) Even w
On Thursday 06 September 2012 Sep, Ariel Molina wrote:
> Hi,
>
> There is a really old, and quite long, list of bugs at Qt, take for example:
> https://bugreports.qt-project.org/browse/QTBUG-9190
>
> Wacom support is broken, it's in fact somewhere between alpha or beta
> state, some tablets work
On Thursday 06 September 2012 Sep, marius.storm-ol...@nokia.com wrote:
> We only had one guy working on it, and he was primarily on OSX. He hadn't
> work for us for years now, hence why these bugs have been piling up.
>
> I think it shouldn't take much for someone who cares and have the HW to get
We only had one guy working on it, and he was primarily on OSX. He hadn't work
for us for years now, hence why these bugs have been piling up.
I think it shouldn't take much for someone who cares and have the HW to get it
back up to scratch.
--
Sent from my Nokia N9On 9/5/12 20:25 ext Ariel Mol
> until it worked correctly
> on a Tablet PC, and expect me to do the same for Qt 5.
Thing is, it's been two years and it still doesn't work well. The bug
tracker is filled with unresolved bugs, begging and ranting.
But the wacom-less default in non-fully-tested platforms would be a good idea.
A
On Thursday 06 September 2012 00:53:37 Ariel Molina wrote:
> 5) Nobody cares about Wacom anyway
I do, every day. I reported bugs for Qt 4, until it worked correctly
on a Tablet PC, and expect me to do the same for Qt 5.
--
Christoph Feck
http://kdepepo.wordpress.com/
KDE Quality Team
__
> I think on Linux the support for tablets and touchscreens is improving
> (I and a couple more coworkers have put in some time on that
> recently); the problem seems to be just on Windows, right?
There are no other reports, but that doesn't mean it's not a problem
in other platforms.
Look at this
On 6 September 2012 00:53, Ariel Molina wrote:
> There is a really old, and quite long, list of bugs at Qt, take for example:
> https://bugreports.qt-project.org/browse/QTBUG-9190
>
> Wacom support is broken, it's in fact somewhere between alpha or beta
> state, some tablets work some others dont.
Hi,
There is a really old, and quite long, list of bugs at Qt, take for example:
https://bugreports.qt-project.org/browse/QTBUG-9190
Wacom support is broken, it's in fact somewhere between alpha or beta
state, some tablets work some others dont. In OSX they work pretty
good, in windows you really
42 matches
Mail list logo
