[Gambas-user] Reading pen pressure from wacom tablets

[Ricardo Díaz Martín]

In addition I attach the project with last modifications.

Regards

2012/8/16 Ricardo Díaz Martín <oceanosoftlapalma at ...626...>

> Ok, this is the information I got:
>
> - When I said crash in the IDE too, it means after the crash in the
> project, if you still moving the pen in the tablet, the IDE got the crash
> with no information (IDE disappear)
> - With gtk+ components the tablet is not detected. Tablet is detected as
> normal mouse. No crash in the project. No crash in the IDE.
> - The event Move, Down, Up are right fired. Work as expected with the pen
> and with the mouse.
> - If you set Tracking property to true in the drawing area control you you
> got the MouseDown event and MouseUp event some times is fired and some
> times no.
> - I got the same crash by compiling gambas with no qt4 optimizations
>
> gdb with gambas3 qt4 no optimizations compiled was:
> Starting program: /usr/local/bin/gbx3
> [Depuración de hilo usando libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [Nuevo Thread 0x7fffea237700 (LWP 20134)]
> [Nuevo Thread 0x7fffe9a36700 (LWP 20135)]
> [Nuevo Thread 0x7fffe37c4700 (LWP 20136)]
>
> Program received signal SIGSEGV, Segmentation fault.
> QBasicAtomicInt::ref (this=0x18700000131) at
> /usr/include/qt4/QtCore/qatomic_x86_64.h:121
> 121                 : "memory");
>
>
> gdb backtrace was:
> #0  QBasicAtomicInt::ref (this=0x18700000131) at
> /usr/include/qt4/QtCore/qatomic_x86_64.h:121
> #1  0x00007ffff5da1184 in QString (other=..., this=0x7fffffffcd10) at
> /usr/include/qt4/QtCore/qstring.h:726
> #2  text (this=0x7fffffffd2b0) at /usr/include/qt4/QtGui/qevent.h:236
> #3  CWidget::eventFilter (this=0x7ffff60082a0, widget=0x986050,
> event=0x7fffffffd2b0) at CWidget.cpp:2822
> #4  0x00007ffff45f1f6c in
> QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*,
> QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
> #5  0x00007ffff4b14806 in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #6  0x00007ffff4b19afc in QApplication::notify(QObject*, QEvent*) () from
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #7  0x00007ffff45f1e9c in QCoreApplication::notifyInternal(QObject*,
> QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
> #8  0x00007ffff4b83643 in ?? () from
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #9  0x00007ffff4b934fe in QApplication::x11ProcessEvent(_XEvent*) () from
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #10 0x00007ffff4bbd0d2 in ?? () from
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #11 0x00007ffff2e80d53 in g_main_context_dispatch () from
> /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #12 0x00007ffff2e810a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #13 0x00007ffff2e81164 in g_main_context_iteration () from
> /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #14 0x00007ffff46213bf in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
> #15 0x00007ffff4bbcd5e in ?? () from
> /usr/lib/x86_64-linux-gnu/libQtGui.so.4
> #16 0x00007ffff45f0c82 in
> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib/x86_64-linux-gnu/libQtCore.so.4
> #17 0x00007ffff45f0ed7 in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib/x86_64-linux-gnu/libQtCore.so.4
> #18 0x00007ffff45f5f67 in QCoreApplication::exec() () from
> /usr/lib/x86_64-linux-gnu/libQtCore.so.4
> #19 0x00007ffff5d9a94f in hook_loop () at main.cpp:777
> #20 0x000000000044262b in main (argc=1, argv=0x7fffffffe138) at gbx.c:417
>
> If I can help you with extra information please say to me.
>
> Regards,
> Ricardo Díaz
>
>
> 2012/8/15 Benoît Minisini <gambas at ...1...>
>
>> Le 15/08/2012 20:09, Ricardo Díaz Martín a écrit :
>> >  When the IDE crash you can see 'core' was generated (but I
>> > don't know where is it to attach to this mail).
>> >
>>
>> Your core file would be too big and useless for me, because the
>> information must be extracted from the same machine that made the core
>> file.
>>
>> But if you find it, you can run 'gdb' on it to get the backtrace of the
>> crash.
>>
>> Regards,
>>
>> --
>> Benoît Minisini
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Gambas-user mailing list
>> Gambas-user at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/gambas-user
>>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: WacomTest-0.0.4.tar.gz
Type: application/x-gzip
Size: 8491 bytes
Desc: not available
URL: <http://lists.gambas-basic.org/pipermail/user/attachments/20120816/81c43fcc/attachment.bin>