public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Qt tutorial 7 - anyone got this to work?
Date: Wed, 28 Mar 2007 16:14:53 +0200	[thread overview]
Message-ID: <200703281615.00022.pauldv@gentoo.org> (raw)
In-Reply-To: <a4a9bfcb0703242327t4033815ag849a73889cf14aff@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

On Sunday 25 March 2007, Daiajo Tibdixious wrote:
> This is probably off-topic, so suggestions to go elsewhere are welcome.
> I reported this to trolltech as a bug, but it doesn't show in their
> task tracker.
> http://doc.trolltech.com/4.2/tutorial-t7.html
> Introduces creating ones own signals & slots.
> slots seem to work fine but signals are not found in a connect call.
> I can't see any difference between the Qt supplied signals (in their
> includes), and my ones.
>
> Another funny is that the Q_OBJECT macro works fine in the Qt includes,
> however if used in my program, linker vtable errors occur caused by
> the virtual functions declared by the macro.

I should probably tell you to read the documentation. What happens is that you 
must include the macro, AND, run moc on your file which creates another C++ 
file that you must also compile (and link). The easiest way to build qt 
projects is to use qmake which handles it for you.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2007-03-28 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25  6:27 [gentoo-amd64] Qt tutorial 7 - anyone got this to work? Daiajo Tibdixious
2007-03-28 14:14 ` Paul de Vrieze [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200703281615.00022.pauldv@gentoo.org \
    --to=pauldv@gentoo.org \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox