- commonqt-devel - mailman3.common-lisp.net

[commonqt-devel] Coerce object to Qt type
by Viktor Ivakin 12 Apr '12

12 Apr '12

Hello! How can one coerce the Qt object to the some Qt type? (coerce qt-object ???) What should I write instead of "???". How can I specify the Qt type here? When I do (#_children parent) where parent is qt form, I have a list of object of some qt types. The one I need are in this list, but his type is QWidget while it should be QTableView. In C++ I can write QTableView *tv = parent->findChild<QTableView *>("view1"); or QTableView *tv = qFindChild<QTableView *>(parent, "view1") but I have no clue how can do this in commonqt. Thanks.

1 0

[commonqt-devel] error instantiating QWebView
by John J. Foerch 27 Sep '11

27 Sep '11

Hello, I ran into some trouble trying to instantiate a QWebView in a little test app. I'm using Qt 4.7 and SBCL on a Debian testing (wheezy) system. Here is the distilled code that produces the error: (in-package :qt-user) (qt:enable-syntax) (ensure-smoke :qtwebkit) (setf qt-user:*application* (qt:make-qapplication "-display" ":0")) (defvar *window* (#_new QWidget)) (defvar *webview* (#_new QWebView *window*)) The error: The value NIL is not of type (UNSIGNED-BYTE 22). [Condition of type TYPE-ERROR] And the backtrace: 0: (QT::UNBASH NIL)[:EXTERNAL] 1: (QT::PERFORM-CAST #<QWebView 0x0066B920> #.(SB-SYS:INT-SAP #X7FFFEFF3C260) 5568 NIL) 2: ((LAMBDA (QT::SUPER)) 15432) 3: ((LABELS QT::RECURSE) 15432) 4: ((LABELS QT::RECURSE) 28936) 5: ((LABELS QT::RECURSE) 5568) 6: (QT::MAP-CPL #<CLOSURE (LAMBDA #) {1003187359}> 5568)[:EXTERNAL] 7: (QT::CACHE! #<QWebView 0x0066B920>) 8: (SB-INT:SIMPLE-EVAL-IN-LEXENV (QT-INTERNAL::|QWebView50| *WINDOW*) #<NULL-LEXENV>) 9: (EVAL (QT-INTERNAL::|QWebView50| *WINDOW*)) Here is what I have learned by debugging and experimenting. The NIL value spoken of comes from FIND-QCLASS-IN-MODULE, which is called by RESOLVE-CAST, which is called by PERFORM-CAST. That value then gets passed to UNBASH, where it results in an error. I don't fully understand the purpose of CACHE! or MAP-CPL, but it looks like MAP-CPL is traversing up the chain of superclasses for QWebView, casting the original object to each base class, and then..? The casts are successful until it gets to the superclass called QPaintDevice (indicated by 15432 in backtrace, frames 3 & 2). In other words, this returns the problematic NIL as its second return value: (qt::resolve-cast (qt::find-qclass "QWebView") (qt::find-qclass "QPaintDevice")) => #.(SB-SYS:INT-SAP #X7FFFEFF3C260) NIL The 28936 in the backtrace (frame 4) is the class QWidget, and for sake of experiment, I tried it, and that cast works: (qt::resolve-cast (qt::find-qclass "QWebView") (qt::find-qclass "QWidget")) => #.(SB-SYS:INT-SAP #X7FFFEFF3C260) 5696 So why does casting from QWebView to QPaintDevice fail? That is about as far as I have been able to go in narrowing down this issue. Hopefully this is helpful to somebody on this mailing list who understands this better than I do. Let me know if I can be of further assistance in debugging & whatnot. Thank you! -- John Foerch

2 4

[commonqt-devel] Custom signal with parameters
by Olaf Merkert 27 Aug '11

27 Aug '11

Hi, how can I define a signal in my custom lisp class, derived for example from QWidget, that accepts as parameter an arbitrary lisp object? Or is that even possible? I really hope it is. What kind of signature would I have to write for that signal? Thanks for your help. Olaf Merkert

1 0

[commonqt-devel] How to invoke Qt methods on Strings/QStrings?
by Olaf Merkert 23 Mar '11

23 Mar '11

Hi, I ran into the next problem: when I evaluate an expression like (#_contains "Hello" "Hel") the first string argument is not treated as an Object but instead commonqt starts looking for a Qt Class named "Hello" and obviously fails. I am aware of the cl function search and cl-ppcre, but I am just curious whether it's possible to use the Qt stuff. I actually started looking at the source code (of commonqt), but couldn't figure out much yet. Regards, Olaf Merkert

2 3

[commonqt-devel] No applicable method setData
by Olaf Merkert 23 Mar '11

23 Mar '11

Hi, I sort of ported one of the Qt4 Tutorials on Models to commonqt, because I want to get to know both Qt4 MVC stuff and commonqt a bit. I more or less just wrote the C++ Code in Lisp syntax. However, there is an error with the bit of code that calls setData (I attached the relevant code): No applicable method setData found on #<QStandardItemModel 0x00886620> with arguments (#<QModelIndex 0x007817A0> #<QDateTime 0x00889540>) [Condition of type SIMPLE-ERROR] I tried wrapping the QDateTime object in a QVariant, but that doesn't help, I get a similar error: No applicable method setData found on #<QStandardItemModel 0x008894D0> with arguments (#<QModelIndex 0x0088A130> #<QVariant 0x0088A2E0>) [Condition of type SIMPLE-ERROR] Qt Documentation says setData expects a QVariant& as the last parameter, but I have no clue how to make one of these. Also, setData works fine with strings. I use sbcl 1.0.40.0.debian on Debian Squeeze, amd64 and the latest commonqt installed via quicklisp (20110320-git). Can anybody help me? I'd like to understand where this problem comes from. Thanks a lot, Olaf Merkert

2 2

[commonqt-devel] CommonQt for newer versions of smoke
by Elliott Slaughter 08 Mar '11

08 Mar '11

I was wondering if CommonQt would be expected to work for newer versions of smoke. I'm wondering because support for Mac OS X has been improving dramatically in the newest version, and I have never been able to make older (even supposedly stable) versions of smoke work on Mac OS X. Undefined symbols: "Smoke::classMap", referenced from: Smoke::findClass(char const*)in commonqt.o Smoke::findClass(char const*)in commonqt.o "Smoke::NullModuleIndex", referenced from: Smoke::idMethod(short, short)in commonqt.o Smoke::idClass(char const*, bool)in commonqt.o Smoke::idClass(char const*, bool)in commonqt.o Smoke::idMethodName(char const*)in commonqt.o Smoke::findClass(char const*)in commonqt.o ld: symbol(s) not found collect2: ld returned 1 exit status This is on Mac OS X 10.6, using Xcode 3.2.5, building an x86_64 binary, with CommonQt from quicklisp, and the newest smoke as of the time of writing. Also note that KDE is moving to git, so the svn repository referenced on the main page is now obsolete. The new git repository is located at: https://projects.kde.org/projects/kde/kdebindings/smoke -- Elliott Slaughter "Don't worry about what anybody else is going to do. The best way to predict the future is to invent it." - Alan Kay

3 7

[commonqt-devel] Undefined symbol in libcommonqt
by Amyn Bennamane 18 Jan '11

18 Jan '11

Hello, When I try to run the CommonQt tutorial by calling the main function, it does not run and I get the following error: Unable to load foreign library (LIBRARY-904). Error opening shared object "/home/amyn/quicklisp/dists/quicklisp/ software/commonqt-20101207-git/libcommonqt.so": /home/amyn/quicklisp/dists/quicklisp/software/commonqt-20101207-git/ libcommonqt.so: undefined symbol: _ZN5Smoke8classMapE. [Condition of type CFFI:LOAD-FOREIGN-LIBRARY-ERROR] when i do "c++filt _ZN5Smoke8classMapE" it gives me: Smoke::classMap But I don't understand the problem. I am using clbuild, sbcl and qt 4.7 under archlinux. -- Amyn

2 4

[commonqt-devel] Microbenchmarks
by David Lichteblau 26 Dec '10

26 Dec '10

Hi, I've added the existing microbenchmark code to the "test" directory of the repository, and cleaned it up a little. (This infrastructure is best benchmark operations in the microsecond to millisecond range. Real-world "macrobenchmarks" should probably be done differently.) The instructions are at the top: ;;;; Evaluate ;;;; (qt::microbench) ;;;; to run these benchmarks on an otherwise idle computer. Results are ;;;; written to the REPL, and in a machine readable format also dribbled ;;;; to files. Files names are, by default, of the form <lisp ;;;; implementation type>.txt. ;;;; ;;;; Notes: ;;;; 1. These are microbenchmarks meant to aid understanding of the ;;;; implementation. They do not necessarily reflect overall or ;;;; real-world performance. ;;;; 2. Since each individual operation is too fast to benchmark, we ;;;; invoke them a large number of times and compute the average run ;;;; time afterwards. ;;;; 3. Before running benchmarks, we choose a repetition time depending ;;;; on how fast (or slow) a simple test case is, so that slow Lisps ;;;; don't waste endless time running benchmarks. ;;;; 4. Benchmarks are run three times, and only the best run of those ;;;; three is reported, to account for issues with background activity ;;;; on the computer ruining the results. ;;;; 5. But you should _still_ run the overall benchmarks several times ;;;; and see how reproducible the numbers are. ;;;; ;;;; There's no tool to parse the output files and drawn graphs yet, but ;;;; there should be. (READ-MICROBENCH-RESULTS already fetches the raw ;;;; sexps from each file though, just to check that they are READable). d.

1 0

[commonqt-devel] Tests and minor changes to :override
by David Lichteblau 26 Dec '10

26 Dec '10

Hi, I have just pushed minor changes and tests for the method overriding syntax. - Added a first test case checking that :override works at all. - Fix function spec parsing to signal an error on invalid specs. - Extend function spec parsing to macroexpand the form. Test changes seem harmless enough that I've pushed them directly to the main repo, but just in case the usual request: Please test! d.

1 0

[commonqt-devel] recent commonqt changes
by Ivan Shvedunov 26 Dec '10

26 Dec '10

Dear colleagues, I've pushed the changes I've accumulated over the last week to my github repository ( https://github.com/ivan4th/commonqt/ ). Please review them and let me know whether I should push some of them to the main repo. Some comments. 1. I've fixed OUTPUT-FILES method on CPP->SO in qt.asd. Without this change, commonqt was being reloaded every time, at least when loading it via quicklisp, due to problems with FASL relocations. Also, SWANK:DELETE-SYSTEM-FILES was deleting only commonqt.so which didn't get restored by make during compilation. 2. When unparseable signal/slot signature was encountered, a rather mysteriously looking error was displayed. I've added a check to MAKE-SLOT-OR-SIGNAL with more readable error message. 3. To make QTYPEP more useful outside CommonQt's own code I've made it recognize type argument specified as string (integer values are still accepted of course). 4. I've added more QVariant conversions to qvariant.lisp. It's still doesn't support all necessary types but at least now it's possible to colorize and decorate these Q*Views. 5. UNMARSHALLER now caches unmarshalled closures. This seems to improve performance a bit in %METHOD-INVOCATION-CALLBACK as it doesn't cache anything itself. Also, I've got rid of redundant NONCONST-NAME function I've introduced previously. I did some tests on a QListView code with custom model with SBCL statistical profiler and seems like all this indeed helps (will later distill that test code into automatic benchmark). 6. The most recent commit is an attempt to cache marshaller closures too, which didn't succeed so far (perhaps I've did something silly there). If you enable cached version of MARSHALLER CommonQt crashes pretty soon when method invocation callbacks happen. This commit shouldn't be pushed to the main repository yet of course. I've tried to research problems with Qt Hemlock. On my machine it causes memory fault soon after (hi::hemlock) on (#_show window) in HI::%INIT-SCREEN-MANAGER. After some debugging with gdb attached to SBCL I've managed to get stack trace of the problem (see attached file). If you google for "QVector<QPair<double, QVariant> >::end" you'll see that the problem is not unique. It happens somewhere in Qt intestines in animation fx related code. Seems like QPropertyAnimation object (it's also QVariantAnimation and QAbstractAnimation) gets destroyed to early. I doubt this problem is directly related to CommonQt changes and most likely it's a bug in Qt which gets triggered by current stack state and other random reasons. I will research it further in coming days. -- Ivan Shvedunov <ivan4th(a)gmail.com> ;; My GPG fingerprint is: 2E61 0748 8E12 BB1A 5AB9 F7D0 613E C0F8 0BC5 2807

2 4