DLL modeless dialog & QT big big problem

Hi all,

My application uses QT to render its interface but I recently encountered a big problem: my application loads a modeless dialog from an external mfc dll; because of mfc architecture PreTranslateMessage isn't called for my modeless dialog, so I thought forwarding the modeless dialog's messages would be the only solution, but now my problem rises:

QT don't support PreTranslateMessage.

I really need a great idea to solve this problem. Please help me.

What is "QT"?

I think you can't help me without knowing QTs, however QT is a developer framework to design GUIs. It is cross-platform so you can have the same gui-feel on every os.

Quote:

---

Originally Posted by VictorN

What is "QT"?

---

http://trolltech.com/products/qt/

Viggy

Well, what is supposed to be done in PreTranslateMessage? Something specific that cannot be handled otherwise (I forgot the terms used in QT for events handling!)

Quote:

---

I forgot the terms used in QT for events handling

---

Slots and Signals ?

It's true, QT doesn't have PreTranslate. I think you need to do your pretranslate stuff in MFC and split it in single events so you can trigger QT.

Quote:

---

Slots and Signals ?

---

Yes!!

Quote:

---

Originally Posted by Skizmo

I think you need to do your pretranslate stuff in MFC and split it in single events so you can trigger QT.

---

Can you better explain what does this mean please?

Quote:

---

My application uses QT to render its interface but I recently encountered a big problem: my application loads a modeless dialog from an external mfc dll; because of mfc architecture PreTranslateMessage isn't called for my modeless dialog, so I thought forwarding the modeless dialog's messages would be the only solution, but now my problem rises

---

Well, which library does exactly display the dialog box? MFC or QT?
What's the real issue? I mean if you can load modelless dialog box in MFC or QT, why you need mixing them?

Actually, I would think that mixing MFC and QT would defeat the purpose of using QT (not cross platform anymore!).

Viggy

Sorry for answering so late but I had some more problems.

I solved this way: I created a thread in the main QT application and loaded the mfc library with the main window as modal.

Modeless dialog with QT application was not an acceptable solution because it needed to implement a message pump dispatcher

This seems a more acceptable solution