SDK FAQ - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:08:33Z

Text replacement - "<syntaxhighlight>" to "<syntaxhighlight lang="C" line>"

← Older revision		Revision as of 19:08, 26 January 2025
Line 3:		Line 3:
	Every [[Exec_Libraries\|Exec Interface]] has a pointer back to the Library which owns it. There is no need to pass the Library pointer around or provide a global Library pointer. The Interface pointer contains all you need.		Every [[Exec_Libraries\|Exec Interface]] has a pointer back to the Library which owns it. There is no need to pass the Library pointer around or provide a global Library pointer. The Interface pointer contains all you need.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct Library *base = IExec->OpenLibrary("intuition.library", 50);		struct Library *base = IExec->OpenLibrary("intuition.library", 50);
	struct IntuitionIFace IIntuition = (struct IntuitionIFace) IExec->GetInterface(base, "main", 1, NULL);		struct IntuitionIFace IIntuition = (struct IntuitionIFace) IExec->GetInterface(base, "main", 1, NULL);
Line 14:		Line 14:
	Use the LIB_IS_AT_LEAST() macro (defined in exec/libraries.h) to determine if a Library you opened is at the minimum version and revision required.		Use the LIB_IS_AT_LEAST() macro (defined in exec/libraries.h) to determine if a Library you opened is at the minimum version and revision required.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct Library *libBase = IExec->OpenLibrary("exec.library", 50);		struct Library *libBase = IExec->OpenLibrary("exec.library", 50);

Line 30:		Line 30:

	If you experiencing issues with DOS constants it is likely your code has not been updated to the newer definitions. To access the obsolete definitions add the following to your source file:		If you experiencing issues with DOS constants it is likely your code has not been updated to the newer definitions. To access the obsolete definitions add the following to your source file:
	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	#include <dos/obsolete.h>		#include <dos/obsolete.h>
	</syntaxhighlight>		</syntaxhighlight>
Line 37:		Line 37:

	If you see warnings like the following:		If you see warnings like the following:
	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	Prefs.cpp:97: error: cannot convert 'Image' to 'Object' in argument passing		Prefs.cpp:97: error: cannot convert 'Image' to 'Object' in argument passing
	</syntaxhighlight>		</syntaxhighlight>
Line 47:		Line 47:

	Starting with SDK 53.24 the [[Application Library]] interfaces, ''application'' and ''prefsobjects'', must be at version 2. That means you need to change your code to do the following:		Starting with SDK 53.24 the [[Application Library]] interfaces, ''application'' and ''prefsobjects'', must be at version 2. That means you need to change your code to do the following:
	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct ApplicationIFace IApplication = (struct ApplicationIFace ) IExec->GetInterface(appBase, "application", 2, NULL);		struct ApplicationIFace IApplication = (struct ApplicationIFace ) IExec->GetInterface(appBase, "application", 2, NULL);
	struct PrefsObjectsIFace IPrefsObjects = (struct PrefsObjectsIFace ) IExec->GetInterface(appBase, "prefsobjects", 2, NULL);		struct PrefsObjectsIFace IPrefsObjects = (struct PrefsObjectsIFace ) IExec->GetInterface(appBase, "prefsobjects", 2, NULL);

Daniel Jedlicka: /* What is version 2 of the application.library interfaces? */

2013-10-14T11:54:52Z

What is version 2 of the application.library interfaces?

← Older revision		Revision as of 11:54, 14 October 2013
Line 44:		Line 44:
	In BOOPSI, objects can be passed around as a pointer to type ''Object''. When Intuition functions expect a specific type they will require it to be passed as a ''struct Gadget '' or ''struct Image '' in arguments. They are still BOOPSI objects but they need to be type casted. This safety mechanism is there to prevent programmers from accidentally passing incorrect BOOPSI object pointers.		In BOOPSI, objects can be passed around as a pointer to type ''Object''. When Intuition functions expect a specific type they will require it to be passed as a ''struct Gadget '' or ''struct Image '' in arguments. They are still BOOPSI objects but they need to be type casted. This safety mechanism is there to prevent programmers from accidentally passing incorrect BOOPSI object pointers.

	= What is version 2 of the ~~application.library~~ interfaces? =		= What is version 2 of the Application Library interfaces? =

	Starting with SDK 53.24 the ~~application.library~~ interfaces ''application'' and ''prefsobjects'' must be at version 2. That means you need to change your code to do the following:		Starting with SDK 53.24 the [[Application Library]] interfaces, ''application'' and ''prefsobjects'', must be at version 2. That means you need to change your code to do the following:
	<syntaxhighlight>		<syntaxhighlight>
	struct ApplicationIFace IApplication = (struct ApplicationIFace) IExec->GetInterface(appBase, "application", 2, NULL);		struct ApplicationIFace IApplication = (struct ApplicationIFace ) IExec->GetInterface(appBase, "application", 2, NULL);
			struct PrefsObjectsIFace IPrefsObjects = (struct PrefsObjectsIFace ) IExec->GetInterface(appBase, "prefsobjects", 2, NULL);
	</syntaxhighlight>		</syntaxhighlight>

Steven Solie: /* What is version 2 of the application.library interface? */

2013-10-13T20:05:35Z

What is version 2 of the application.library interface?

← Older revision		Revision as of 20:05, 13 October 2013
Line 44:		Line 44:
	In BOOPSI, objects can be passed around as a pointer to type ''Object''. When Intuition functions expect a specific type they will require it to be passed as a ''struct Gadget '' or ''struct Image '' in arguments. They are still BOOPSI objects but they need to be type casted. This safety mechanism is there to prevent programmers from accidentally passing incorrect BOOPSI object pointers.		In BOOPSI, objects can be passed around as a pointer to type ''Object''. When Intuition functions expect a specific type they will require it to be passed as a ''struct Gadget '' or ''struct Image '' in arguments. They are still BOOPSI objects but they need to be type casted. This safety mechanism is there to prevent programmers from accidentally passing incorrect BOOPSI object pointers.

	= What is version 2 of the application.library ~~interface~~? =		= What is version 2 of the application.library interfaces? =

	Starting with SDK 53.24 the application.library ~~interface~~ must be at version 2. That means you need to change your code to do the following:		Starting with SDK 53.24 the application.library interfaces ''application'' and ''prefsobjects'' must be at version 2. That means you need to change your code to do the following:
	<syntaxhighlight>		<syntaxhighlight>
	struct ApplicationIFace IApplication = (struct ApplicationIFace) IExec->GetInterface(appBase, "~~main~~", 2, NULL);		struct ApplicationIFace IApplication = (struct ApplicationIFace) IExec->GetInterface(appBase, "application", 2, NULL);
	</syntaxhighlight>		</syntaxhighlight>

	The interface ~~change~~ ~~was~~ necessary to fix an API ~~flaw~~. Interfaces are not backwards or forwards compatible so they must be specified precisely as well.		The interface changes were necessary to fix API flaws. Interfaces are not backwards or forwards compatible so they must be specified precisely as well.

Steven Solie at 02:17, 13 October 2013

2013-10-13T02:17:11Z

← Older revision		Revision as of 02:17, 13 October 2013
Line 43:		Line 43:

	In BOOPSI, objects can be passed around as a pointer to type ''Object''. When Intuition functions expect a specific type they will require it to be passed as a ''struct Gadget '' or ''struct Image '' in arguments. They are still BOOPSI objects but they need to be type casted. This safety mechanism is there to prevent programmers from accidentally passing incorrect BOOPSI object pointers.		In BOOPSI, objects can be passed around as a pointer to type ''Object''. When Intuition functions expect a specific type they will require it to be passed as a ''struct Gadget '' or ''struct Image '' in arguments. They are still BOOPSI objects but they need to be type casted. This safety mechanism is there to prevent programmers from accidentally passing incorrect BOOPSI object pointers.

			= What is version 2 of the application.library interface? =

			Starting with SDK 53.24 the application.library interface must be at version 2. That means you need to change your code to do the following:
			<syntaxhighlight>
			struct ApplicationIFace IApplication = (struct ApplicationIFace) IExec->GetInterface(appBase, "main", 2, NULL);
			</syntaxhighlight>

			The interface change was necessary to fix an API flaw. Interfaces are not backwards or forwards compatible so they must be specified precisely as well.

Steven Solie at 14:52, 12 October 2013

2013-10-12T14:52:00Z

← Older revision		Revision as of 14:52, 12 October 2013
Line 1:		Line 1:
			= How do I get the Library base pointer provided an Interface pointer? =

			Every [[Exec_Libraries\|Exec Interface]] has a pointer back to the Library which owns it. There is no need to pass the Library pointer around or provide a global Library pointer. The Interface pointer contains all you need.

			<syntaxhighlight>
			struct Library *base = IExec->OpenLibrary("intuition.library", 50);
			struct IntuitionIFace IIntuition = (struct IntuitionIFace) IExec->GetInterface(base, "main", 1, NULL);

			IDOS->Printf("Intuition Library pointer=%p\n", IIntuition->Data.LibBase);
			</syntaxhighlight>

	= How do I check for a minimum Library version and revision? =		= How do I check for a minimum Library version and revision? =

Steven Solie at 14:44, 12 October 2013

2013-10-12T14:44:29Z

← Older revision		Revision as of 14:44, 12 October 2013
Line 1:		Line 1:
			= How do I check for a minimum Library version and revision? =

			Use the LIB_IS_AT_LEAST() macro (defined in exec/libraries.h) to determine if a Library you opened is at the minimum version and revision required.

			<syntaxhighlight>
			struct Library *libBase = IExec->OpenLibrary("exec.library", 50);

			if ( LIB_IS_AT_LEAST(libBase, 53, 58) )
			{
			IDOS->Printf("Found the correct version!\n");
			}
			else
			{
			IDOS->Printf("Minimum version 53.58 required.\n");
			}
			</syntaxhighlight>

	= What are all these new DOS errors I'm seeing? =		= What are all these new DOS errors I'm seeing? =

Steven Solie at 18:21, 8 October 2013

2013-10-08T18:21:41Z

@@ Line 1: / Line 1: @@
-= I'm getting all sorts of errors related to DOS =
+= What are all these new DOS errors I'm seeing? =
 If you experiencing issues with DOS constants it is likely your code has not been updated to the newer definitions. To access the obsolete definitions add the following to your source file:
@@ Line 5: / Line 5: @@
 #include <dos/obsolete.h>
 </syntaxhighlight>

Steven Solie: Created page with "= I'm getting all sorts of errors related to DOS = If you experiencing issues with DOS constants it is likely your code has not been updated to the newer definitions. To acce..."

2013-10-08T18:05:08Z

Created page with "= I'm getting all sorts of errors related to DOS = If you experiencing issues with DOS constants it is likely your code has not been updated to the newer definitions. To acce..."

New page

= I'm getting all sorts of errors related to DOS =

If you experiencing issues with DOS constants it is likely your code has not been updated to the newer definitions. To access the obsolete definitions add the following to your source file:
<syntaxhighlight>
#include <dos/obsolete.h>
</syntaxhighlight>