API Question Breaking VC off into seperate class

[csanders]

"Debug information binaries not available, would you like to continue any way?"

I think that comes up if you try to debug with a "Release" build.

Try to change it to the "Debug" build (I believe this is set under Build->Configuration Manager).

Trust me, learning the Debugger is the best thing you can do. Stepping through the code line by line might answer your question in 5 minutes.

FYI, you can set a breakpoint on a line by putting the typing cursor thing on that line, and hitting F9.

 

[orb]

The question is why is moving the the function and switch variables from the LM vessel class to the LM_Cockpit class causing them to fail?

You could find out why in the debugger...

But anyway we're getting side tracked.

The issue is not the debugger it's parsing the scenario file.

The issue could be resolved either when you posted the full code for someone to run it through debugger, or if you could debug it by stepping through the lines in your code by yourself.

I think that comes up if you try to debug with a "Release" build.

No. That's just an information that orbiter.exe hasn't been built with debug information. It doesn't stop you from debugging your module though, which hasn't been loaded yet and which contains the debug information (if it's been built to have it).

 

[csanders]

No. That's just an information that orbiter.exe hasn't been built with debug information. It doesn't stop you from debugging your module though, which hasn't been loaded yet and which contains the debug information (if it's been built to have it).

It's been a while since I've done a .dll debug, but won't it do the same if you debug in "Release"???

Anyway, back to the point. This is still a problem: "I click yes and get a blank orbiter launch pad screen. "

Are you sure the "Working Directory" is Orbiter's root?

Also, it being a while since I've done a .dll debug, does the generated .dll from Visual Studios have to be in the directory that Orbiter expects it to be? (anyone know?) I would think it would, because otherwise Orbiter will use the .dll in that directory instead, and Visual Studio won't "know" that that .dll it generates is the one it should be debugging.

Trust me Hlynkacg, once you get debugging working, you will be kicking yourself for not doing it sooner. VS has one of the best debuggers in the biz. Learning it will save you tons of effort in the future, and even teach you a thing or two about what is happening "behind the scenes" so to speak.

 

[orb]

Also, it being a while since I've done a .dll debug, does the generated .dll from Visual Studios have to be in the directory that Orbiter expects it to be? (anyone know?)

It has to be in the directory Orbiter expects it to be.

If you use Orbiter property sheets, the linker output file is set automatically to "$(ModuleDir)\$(ProjectName).dll" for a vessel (by "Orbiter vessel" property sheet), and to "$(ModuleDir)\Plugins\$(ProjectName).dll" for a plug-in (by "Orbiter plugin" property sheet), if you don't override them with your values in properties of your project, and of course $(ModuleDir) macro is set (by "Orbiter" property sheet) to "$(OrbiterDir)\Modules" too.

(The $(OrbiterDir) macro is the only one you set by yourself and only first time you use property sheets for new installation of Orbiter (or if you moved Orbiter directory to a new location) -- in "orbiterroot" property sheet. Neither "orbiterroot" nor "Orbiter" sheets need to be added to the project, because they are already included from "Orbiter vessel" or "Orbiter plugin" sheets.)


BTW, of couse for Debug configuration you also add "Orbiter debug" property sheet, which takes care of setting up the debug information for you. The only properties you set then are the command to run: "$(OrbiterDir)\orbiter.exe", and the working directory: "$(OrbiterDir)". It's really much faster and simpler than configuring the whole project by yourself.

 

[csanders]

It's really much faster and simpler than configuring the whole project by yourself.

Only if you know how to use property sheets!
(sadly, I don't)

 

[Notebook]

Exactly, any chance any one can explain how ( on Orbiter/Wiki?) what property sheets do how you make them, what can go wrong?

To me they are just a jumble of $, brackets, [] {} /.../... \... and similar. Makes no sense, and no help at all?

N.

 

[orb]

Only if you know how to use property sheets!
(sadly, I don't)

<PostID: 378725> (instructions are for VC++ 2010; for VC++ 2005/2008 ommit converting and switching to "Expert" settings).

 

[Notebook]

Yes, I've seen that thread, but I don't understand the basics of what a "Property Sheet" is, why I need it, what is its advantage?
...Remember a lot of folk like me have no experience of programming, you may have noticed....

N.

 

[Hlynkacg]

For the 3rd time yes I'm sure I'm using orbiters directory as my working directory, and yes I'm using the orbiter property sheets.

seeing as this is not my problem, and from what I gather reading the VS support sites wouldn't adress the whole VS2010 freezing issue if it were, I'm now in the process of unintalling both VS2010, the runtime enviroment, and Orbiter.

I'll try again with a fresh install of each and get back to you.