Displaying a property sheet

[oliver_mpt]

Hello,

I have a DLL which loads along with FSX, and the user can get info from my DLL through the add-on menu which launch a simple windows dialog box containing the information.

Now I want to make something more sophisticated with propertysheet and propertypages, so I have followed the standard procedure (creating property pages, loading them in the sheet with AddPage(&MyPageN) ). When I call my property sheet from within my DLL with :

CMyDialog dlg; // This is my property sheet class
dlg.DoModal()

I get an assertion failure in afxwin1.inl :
_AFXWIN_INLINE HINSTANCE AFXAPI AfxGetResourceHandle()
{ ASSERT(afxCurrentResourceHandle != NULL);
return afxCurrentResourceHandle; }

Is there something special when using that kind of dialog from within a simconnect DLL ??

In particular, is there somepoint I missed with the parent window ?

Oliver

 

[oliver_mpt]

Hello again,

I forgot to tell : before trying to display my property sheet, I have switched to dialog mode in FSX with simconnect.

The kind of thing I want is the dialog you get with FSUIPC, with the different tabs.

Oliver

 

[oliver_mpt]

Me again,

I'm making my own thread by myself
I have changed the propety sheet for a basic dialog with two buttons that does no more than the windows Message Box, and I have exactly the same problem.
1 - I switch FS to dialog mode
2 - I try to display some UI element. Property sheets or Visual studio made dialog fails, while standard message Box works perfectly.

Any idea ?

 

[oliver_mpt]

Come on,

tell me if I'm probably doing something stupid, or if there's a known limitation with windows dialogs in FSX dialog mode.

oliver

 

[beatle]

There are lots of known limitations with doing GDI based UI from within the FS environment, which is why we don't suggest doing it :-> But, if you are going to try it, some things to try:

Make sure you have set the parent of your dialog window to be the main FS window (do a FindWindow on FS98MAIN) - if you don't do this, then your window will be under FS (especially in full screen mode). If you can live with your window only being visible in windowed mode, you can also make it a top-level window (so it shows up on the task bar display) - although if you can live with this, you could probably just make the client be an external EXE based app instead and avoid the issue altogether :->

Set FS into Dialog Mode (sounds like you are already handling this part) - the reason for this is that occasionally GDI and DirectX don't play nice together causing anomilies in the DirectX display, so in Dialog Mode, we black out the 3D windows so if there are any anomolies, they aren't visible :->

Another thing to try, use standard WIN32 API calls to create/display your dialog intead of using MFC (since FS also uses MFC internally, its possible MFC is in a weird state).

 

[oliver_mpt]

Thanks a lot Beatle !

I'll try following these guidelines, and I'll report later

Merry Christmas !

Oliver

 

[oliver_mpt]

Problem Solved :

Another thing to try, use standard WIN32 API calls to create/display your dialog intead of using MFC (since FS also uses MFC internally, its possible MFC is in a weird state).

You can use MFC dialog in FSX dialog mode.
The problem was to manage the MFC internal state. I included a :
AFX_MANAGE_STATE(AfxGetStaticModuleState());
macro a the beginning of my dispatch callback function and that did it !

best regards

Oliver