Thanks!

I'll post the solution here, in case anyone else wants it. It bugs me though, that it can't be done without creating a derived class.

If anyone finds a mistake, I'd appreciate it if you tell me.

That's just how Qt rolls: signals here, but events there. There is nothing a signal couldn't do what an event can do (from my POV).
However, if you have a crappy signal and slot implementation (slow, preprocessor-based, no real namespace support, no compile-time checks, no flexible parameter binding, only QSignalMapper or private slots) then you try everything to get around it, at least when performance and correctness is important. Well, and turns out that this actually *is* important if you write frameworks or libraries.

That's why you have this seemingly arbitrary separation between signals and events in Qt, even though it makes no sense to the application developer (which would almost always prepare a signal over an event, simply because it is easier to use and more flexible).

You'll soon get used to the Qt mantra of deriving custom classes for every little feature though (I am not saying that this is a good habit).

Mikhas, you seem to know much about Qt.

Could you please view this thread?
It would be great if you could say something about that issue.

I only had a brief look at the example, it probably crashes because something else is closing your QDialog before you get to handle the dialog's response. But just looking at the code is not as helpful as simply running it through the debugger. So if you turn the code snippet into a compiling testcase (which still reproduces the crash) then I can help you.

The entire source of the application (with Qt creator project files and all) is there at another post.

Hello
guys im very very new to qt and development stuff so you got to excuse me...
ok so i have maemo SDK, scratchbox, and qt SDk installed on my ubuntu lucid ( 10.04 )
i created in qt-creator a hello-world app and it's directory contains :
-/qml/hellowrld/main.qml
-/qmlapplicationviewer/
--qmlapplicationviewer.cpp
--qmlapplicationviewer.h
--qmlapplicationviewer.pri
-helloworld.desktop
-helloworld.pro.user
-main.cpp
-helloworld.png
-helloworld.pro
-helloworld.svg

what steps i should do to compile that source and result a binary that i could send it to my N900 and run it
would really appreciate a short step by step guide

./sifo

I'm not so sure there's a perfectly short guide to doing it. I think the most important item is probably to get the Maemo Toolchain for your SDK, if you haven't already. You can do this by starting up the SDK Maintenance Tool, going to the Package Manager, and drilling down to Qt SDK -> Development Tools -> Maemo Toolchain.

(At least, this is how I'm doing it. I haven't updated my SDK in almost a year though, so things might have changed a bit.)

Once you've got the toolchain, you should be able to set up Maemo 5 as one of the targets for your project. (There's a "Projects" icon on the left side of my Qt Creator window that allows you to edit project targets.)

There's a scratchbox environment you can use to simulate a N900 for testing purposes, and a wizard to simplify installing apps onto a real N900. You can also just copy a binary on to your device and run it directly, if you prefer.

Probably the best resource for me is the Qt Maemo/Meego Support Page, which contains links to most of the Maemo-related documentation on their website.

So yeah, nothing extremely quick and easy to get you started, but once you've got all the bits and pieces in place, it's easy to build binaries and get them on to your device.

Here's some pages I bookmarked in Firefox from when I setup my environment a couple of months ago.

http://wiki.maemo.org/Documentation/...-based_systems

http://wiki.maemo.org/Documentation/...own_the_SDK_UI

http://talk.maemo.org/showthread.php?t=68684&page=2

Qt "Build" will create files that are upload-able to extras.
This makes a source.changes, dsc and tar files for the autobuilder.

To create armel debs I move the files to scratchbox MyDocs directory and run in scratchbox armel targets...

This makes a armel.deb, and armel sources.
I install the armel.deb to my N900 to test.

If the package works OK, I upload the file created by Qt "build" to autobuilder.

Remember if using this method to change your compat file to 5 as 7 will not work in scratchbox.

I usually prefer using madde, makes my life easier, and works as well.

Just install madde on N900, add maemo toolchain from the QtSDK update tool, go to options -> linux devices -> device configuration on QtCreator and let the wizard guide you.

Thank you all for your replies
And here come the story how can i copy stuff from / to scratchbox (MyDocs) ?

./sifo