Difference between revisions of "Talk:Writing Extensions"
(→This entire article is out of date) |
(→This entire article is out of date: rescinding my comment...) |
||
| Line 12: | Line 12: | ||
"An Event is formally called a Forward." is a very bad way to phrase this. Source games have [[Game Events (Source)|game events]], and forwards are ''not'' the same as those. --[[User:Powerlord|Powerlord]] 02:32, 8 June 2011 (UTC) | "An Event is formally called a Forward." is a very bad way to phrase this. Source games have [[Game Events (Source)|game events]], and forwards are ''not'' the same as those. --[[User:Powerlord|Powerlord]] 02:32, 8 June 2011 (UTC) | ||
| − | |||
| − | |||
| − | |||
Latest revision as of 10:27, 19 May 2014
Visual Studio section woefully out of date
The Visual Studio sections seem to miss a lot of things that they should list. The SourceMod source public\sample_ext directory now contains solutions and projects for Visual Studio 2005 (msvc8), 2008 (msvc9), and 2010 (msvc10).
However, the configuration for this, such as the Linker Input tab, have a bunch of variables that aren't explained. For instance, where does one set $(HL2SDKOBVALVE), the variable that tells it where the HL2SDK files for HL2:DM, CS:S, DOD:S, and TF2 are located? Since this will have a different location on each system, this is a variable that needs to be set by the programmer writing the extension.
I admit, maybe this is because I haven't ever used Visual Studio for C++ before, but this sort of thing seems like the kind of thing that should be explained in the Setting up Visual Studio section. --Powerlord 02:25, 1 June 2011 (UTC)
- Incidentally, I later realized those were likely environment variables. --Powerlord 02:45, 1 June 2011 (UTC)
"An Event is formally called a Forward."
"An Event is formally called a Forward." is a very bad way to phrase this. Source games have game events, and forwards are not the same as those. --Powerlord 02:32, 8 June 2011 (UTC)
