Talk:Beginner's Basic Plugin Guide - Revision history

Culix: add section title and comment attribution

2010-05-21T15:25:48Z

add section title and comment attribution

Daniel15: /* Next Steps */

2009-11-25T05:51:52Z

‎Next Steps

Daniel15 at 05:51, 25 November 2009

2009-11-25T05:51:32Z

SMonty: /* Basic gen_empty.dll File Crashes WinAMP On Start Of WinAMP. */

2009-09-21T16:33:41Z

‎Basic gen_empty.dll File Crashes WinAMP On Start Of WinAMP.

Ace Frahm: Empty Blank Generic Plugin Example Crashes WinAMP 5.56 On Launch

2009-09-20T22:44:14Z

Empty Blank Generic Plugin Example Crashes WinAMP 5.56 On Launch

SMonty: /* Questions and TODO */

2009-07-02T18:10:41Z

‎Questions and TODO

SMonty: /* Questions and TODO */

2009-07-02T17:51:54Z

‎Questions and TODO

SMonty: /* Questions and TODO */

2009-07-02T17:51:08Z

‎Questions and TODO

SMonty: /* Questions and TODO */

2009-07-02T17:35:06Z

‎Questions and TODO

Culix: /* Next Steps */

2009-06-10T14:54:56Z

‎Next Steps

@@ Line 22: / Line 22: @@
 <p>The point of the extern "C" is to tell the linker not to perform C++ name mangling on the function name.  This is necessary when some other application needs to invoke the method and therefore needs to use a name that is easier to use.  Technically it doesn't matter whether you put them in a header or cpp file and it boils down to the more common reasons why you choose to put things in header files rather than including them in the cpp file.</p>
 ===Basic gen_empty.dll File Crashes WinAMP On Start Of WinAMP.===
 I have turned off pre-compiled headers in VS 2008 Pro.
@@ Line 36: / Line 37: @@
 I even commented out the MessageBox-es so the functions would do NOTHING, and tried the resulting gen_empty.dll.
-'''What is wrong with this generic, blank plugin source code that causes WinAMP 5.56 to fail?'''
+'''What is wrong with this generic, blank plugin source code that causes WinAMP 5.56 to fail?''' <small>—The preceding unsigned comment was added by [[User:Ace Frahm|Ace Frahm]] ([[User talk:Ace Frahm|talk]] • [[Special:Contributions/Ace Frahm|contribs]]) 22:44, 20 September 2009.</small><!-- Template:Unsignedr -->
 <source lang=cpp>
@@ Line 123: / Line 124: @@
 Hi, I examined your code and could see nothing that would cause Winamp to crash.  I then copied the code you posted to my development machine, compiled it and moved it to the plugins directory and Winamp worked fine.  I tested this on 5.56 and 5.57.
-My thought would be to look at some of the project options you may have set as I believe the C++ code is not the problem.  My first thought might be the packing for structures.
+My thought would be to look at some of the project options you may have set as I believe the C++ code is not the problem.  My first thought might be the packing for structures. <small>—The preceding unsigned comment was added by [[User:SMonty|SMonty]] ([[User talk:SMonty|talk]] • [[Special:Contributions/SMonty|contribs]]) 16:33, 21 September 2009 .</small><!-- Template:Unsignedr -->
 ==Next Steps==

@@ Line 128: / Line 128: @@
 I think a good extension of this article would be to answer the user's question of "Okay, now what?". If we could give them hints about where to go next, possibly depending on the type of plugin they want to write, that might be useful. This may just involve fleshing out the guide articles for each type of plugin and then linking to those... unless someone can think of something better? --[[User:Culix|Culix]] 14:54, 10 June 2009 (UTC)
 You're making a CLR library (which gives you full access to the .NET Framework), but using the Win32 MessageBox() call. Why? You can just add a reference to System.Windows.Forms and then use System::Windows::Forms::MessageBox::Show("Message")
 :)
 --[[User:Daniel15|Daniel15]] 05:51, 25 November 2009 (UTC)

← Older revision		Revision as of 05:51, 25 November 2009
Line 127:		Line 127:
	==Next Steps==		==Next Steps==
	I think a good extension of this article would be to answer the user's question of "Okay, now what?". If we could give them hints about where to go next, possibly depending on the type of plugin they want to write, that might be useful. This may just involve fleshing out the guide articles for each type of plugin and then linking to those... unless someone can think of something better? --[[User:Culix\|Culix]] 14:54, 10 June 2009 (UTC)		I think a good extension of this article would be to answer the user's question of "Okay, now what?". If we could give them hints about where to go next, possibly depending on the type of plugin they want to write, that might be useful. This may just involve fleshing out the guide articles for each type of plugin and then linking to those... unless someone can think of something better? --[[User:Culix\|Culix]] 14:54, 10 June 2009 (UTC)
		+
		+	You're making a CLR library (which gives you full access to the .NET Framework), but using the Win32 MessageBox() call. Why? You can just add a reference to System.Windows.Forms and then use System::Windows::Forms::MessageBox::Show("Message")
		+	:)
		+
		+	--[[User:Daniel15\|Daniel15]] 05:51, 25 November 2009 (UTC)

@@ Line 120: / Line 120: @@
 //-----------------------------------------------------------------</source>
 ==Next Steps==
 I think a good extension of this article would be to answer the user's question of "Okay, now what?". If we could give them hints about where to go next, possibly depending on the type of plugin they want to write, that might be useful. This may just involve fleshing out the guide articles for each type of plugin and then linking to those... unless someone can think of something better? --[[User:Culix|Culix]] 14:54, 10 June 2009 (UTC)

@@ Line 21: / Line 21: @@
 <p>The point of the extern "C" is to tell the linker not to perform C++ name mangling on the function name.  This is necessary when some other application needs to invoke the method and therefore needs to use a name that is easier to use.  Technically it doesn't matter whether you put them in a header or cpp file and it boils down to the more common reasons why you choose to put things in header files rather than including them in the cpp file.</p>
 ==Next Steps==
 I think a good extension of this article would be to answer the user's question of "Okay, now what?". If we could give them hints about where to go next, possibly depending on the type of plugin they want to write, that might be useful. This may just involve fleshing out the guide articles for each type of plugin and then linking to those... unless someone can think of something better? --[[User:Culix|Culix]] 14:54, 10 June 2009 (UTC)

@@ Line 8: / Line 8: @@
 * How do the naming conventions work for plugins? It seems more complicated than simply naming your file 'gen_*' or 'ml_*'.
-<p>The answer to this is complicated, as so much with Winamp.  The prefix is actually used by Winamp.exe to find plugins and identify what type they are.  There is another way to create plugins that does not require the prefix.  This second way is called Wasabi.  Wasabi is a way to 'share' code among components of a software system (i.e., Winamp).  Wasabi dlls do not need the prefix.  We'll get to Wasabi if we keep writing these kinds of tutorials.  Is there something specific about the prefixes that leads you to believe that there is a 'real' answer?  Maybe I can investigate further.
+<p>The answer to this is complicated, as so much with Winamp.  The prefix is actually used by Winamp.exe to find plugins and identify what type they are.  There is another way to create plugins that does not require the prefix.  This second way is called Wasabi.  Wasabi is a way to 'share' code among components of a software system (i.e., Winamp).  Wasabi dlls do not need the prefix.  We'll get to Wasabi if we keep writing these kinds of tutorials.  Is there something specific about the prefixes that leads you to believe that there is a 'real' answer?  Maybe I can investigate further.</p>
 * For the "cannot convert parameter from 'const char [x]' to 'LPCTSTR'" error, which option from the [http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/c1b08c0a-a803-41c3-ac8c-84eba3be1ddb MSDN FAQ] should we actually use? Is it better to change the project settings to use a multi-byte character set?
-<p>I would not change the project settings and instead use the L"" or _TEXT constructs to indicate that the strings are wide strings.  Winamp programmers prefer to be even more specific and actually call the MessageBoxW() or MessageBoxA() methods to make it absolutely clear as to which function and what form the input is in (this would make the project switch meaningless).  Since Winamp is a very popular application around the world it is best to use UNICODE.
+<p>I would not change the project settings and instead use the L"" or _TEXT constructs to indicate that the strings are wide strings.  Winamp programmers prefer to be even more specific and actually call the MessageBoxW() or MessageBoxA() methods to make it absolutely clear as to which function and what form the input is in (this would make the project switch meaningless).  Since Winamp is a very popular application around the world it is best to use UNICODE.</p>
 * Why do some people put their 'extern "C" __declspec' code in the header and others in the .cpp? Does it matter?
 ==Next Steps==
 I think a good extension of this article would be to answer the user's question of "Okay, now what?". If we could give them hints about where to go next, possibly depending on the type of plugin they want to write, that might be useful. This may just involve fleshing out the guide articles for each type of plugin and then linking to those... unless someone can think of something better? --[[User:Culix|Culix]] 14:54, 10 June 2009 (UTC)

← Older revision		Revision as of 14:54, 10 June 2009
Line 9:		Line 9:
	* For the "cannot convert parameter from 'const char [x]' to 'LPCTSTR'" error, which option from the [http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/c1b08c0a-a803-41c3-ac8c-84eba3be1ddb MSDN FAQ] should we actually use? Is it better to change the project settings to use a multi-byte character set?		* For the "cannot convert parameter from 'const char [x]' to 'LPCTSTR'" error, which option from the [http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/c1b08c0a-a803-41c3-ac8c-84eba3be1ddb MSDN FAQ] should we actually use? Is it better to change the project settings to use a multi-byte character set?
	* Why do some people put their 'extern "C" __declspec' code in the header and others in the .cpp? Does it matter?		* Why do some people put their 'extern "C" __declspec' code in the header and others in the .cpp? Does it matter?
		+
		+	==Next Steps==
		+	I think a good extension of this article would be to answer the user's question of "Okay, now what?". If we could give them hints about where to go next, possibly depending on the type of plugin they want to write, that might be useful. This may just involve fleshing out the guide articles for each type of plugin and then linking to those... unless someone can think of something better? --[[User:Culix\|Culix]] 14:54, 10 June 2009 (UTC)