I don't think folder location is a problem but not sure, need to link to the correct lib, managed, or checkout the legacy folder perhaps you need one of those, and also will need to specify a manifest

Well, the SimConnect.lib is here:

 

C:\FSX_SDK\SDK\Core Utilities Kit\SimConnect SDK\inc\SimConnect.lib

 

I reference it per the SimConnect SDK here: http://msdn.microsoft.com/en-us/library/cc526983.aspx.

 

It says to add simconnect.lib to Linker/Input/Additional Dependencies and I have done that but it still can't 'see' it when I do a build.

 

>and also will need to specify a manifest

I'll google that as I have no idea what that is but I do see a Sample.exe.manifest file.

 

>checkout the legacy folder

I'll try to reference the .lib file in that folder.

 

UPDATE:

 

I added "C:\FSX_SDK\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1\SimConnect.lib"

to

Linker/Input/Additional Dependencies. So this now has two references:

C:\FSX_SDK\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1\SimConnect.lib

C:\FSX_SDK\SDK\Core Utilities Kit\SimConnect SDK\inc\SimConnect.lib

 

and it builds the .exe OK for Release, so that's good. But when I try to build it for Debug I get this:

 

1>------ Build started: Project: TextMenu, Configuration: Debug Win32 ------

1>LINK : fatal error LNK1181: cannot open input file 'C:\FSX_SDK\SDK\Core Utilities Kit\SimConnect SDK\inc\SimConnect.lib'

========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

 

I still have to read up on the manifest.

The directory that you've added to the project is wrong. You have specified "inc\SimConnect.lib" and the library does not exist in that directory. The correct directory is "lib\SimConnect.lib".

@cfsops

 

Yes, you are correct. I edited to 'lib' and now both Debug and Release compile and link OK.

 

Thank you...

Very cool. I'm glad it's working for you now!

I've been looking at the SimConnect SDK and running the TextMenu example.

 

I'd like to be able to pop up a text window (as the example does) but when I click on one of the items in the window, I'd like to open another textmenu window.

 

I made an edit in the code snippet below. It is commented out so you can see which line I added.

 

A new textmenu window will open when I click on an item in the first popup textmenu window, but there doesn't seem to be a solid behavior pattern when I do this. Sometings I click on the first item in the first window and another window opens (as desired) but at other times it does not open. I can click on the 2nd or 3rd item and sometimes open the second window and sometimes not.

 

So, I guess I don't understand how this callback structure works. Where I'm going with this is that I want to be able to click on item 1 in the first window and open another window with context textual data for item 1. Then I want to click on item2 and open a window for that with textual data related to item2.

 

So, I created a new enum EVENT_MENU_2 and defined a new Menu2 string to display in window 2 (which it does when it works).

 

Because of the unreliable behavior in trying to open a 2nd window, I guess that means I don't understand how the callback structure works.

 

The snippet of code below is where I inserted a line to open a textmenu window.

 

This snippet of code is in the "CALLBACK MySignalProc(SIMCONNECT_RECV* pData, DWORD cbData, void *pContext)" function.

 

case EVENT_MENU_1:

// Respond to the users menu selection

printf("\n");

printf( MenuText( (SIMCONNECT_TEXT_RESULT) evt->dwData ) );

                    // line I added: SimConnect_Text(hSimConnect, SIMCONNECT_TEXT_TYPE_MENU, 0, EVENT_MENU_2, sizeof(Menu2), (void*)Menu2);

break;

 

Thank you for any help...