Workbench Library - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:24:15Z

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

← Older revision		Revision as of 19:24, 26 January 2025
Line 70:		Line 70:
	The WBStartup message, whose structure is outlined in <workbench/startup.h>, has the following structure elements:		The WBStartup message, whose structure is outlined in <workbench/startup.h>, has the following structure elements:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct WBStartup		struct WBStartup
	{		{
Line 106:		Line 106:
	Each argument is a struct WBArg and has two parts: wa_Name and wa_Lock.		Each argument is a struct WBArg and has two parts: wa_Name and wa_Lock.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct WBArg		struct WBArg
	{		{
Line 128:		Line 128:
	The following example will display all WBArgs if started from Workbench, and all Shell arguments if started from the Shell.		The following example will display all WBArgs if started from Workbench, and all Shell arguments if started from the Shell.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	/* prargs.c		/* prargs.c
	**		**
Line 236:		Line 236:
	When Workbench notifies an application of AppWindow, AppIcon, or AppMenuItem activity, it sends an AppMessage to the application's message port (from <workbench/workbench.h>):		When Workbench notifies an application of AppWindow, AppIcon, or AppMenuItem activity, it sends an AppMessage to the application's message port (from <workbench/workbench.h>):

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	#define AM_VERSION 1		#define AM_VERSION 1

Line 279:		Line 279:
	AppWindows, AppIcons and AppMenuItems extend the user's ability to perform operations with the Workbench iconic interface. They all provide graphical methods for passing arguments to a running application. In order to manage AppWindows, AppIcons and AppMenuItems, the Amiga OS includes these Workbench library functions:		AppWindows, AppIcons and AppMenuItems extend the user's ability to perform operations with the Workbench iconic interface. They all provide graphical methods for passing arguments to a running application. In order to manage AppWindows, AppIcons and AppMenuItems, the Amiga OS includes these Workbench library functions:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct AppIcon AddAppIconA( ULONG, ULONG, char , struct MsgPort , struct FileLock ,		struct AppIcon AddAppIconA( ULONG, ULONG, char , struct MsgPort , struct FileLock ,
	struct DiskObject , struct TagItem );		struct DiskObject , struct TagItem );
Line 298:		Line 298:
	For convenience, this example code uses GetDefDiskObject() to create the icon imagery for the AppIcon. Applications should never do this. Use your own custom imagery for AppIcons instead.		For convenience, this example code uses GetDefDiskObject() to create the icon imagery for the AppIcon. Applications should never do this. Use your own custom imagery for AppIcons instead.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	/* appicon.c		/* appicon.c
	/* Works from the Shell (CLI) only */		/* Works from the Shell (CLI) only */
Line 413:		Line 413:
	The example starts up the More program as a separate, asynchronous process using the SystemTags() function. When the AppMenuItem has been activated five times, the program exits after freeing any system resources it has used.		The example starts up the More program as a separate, asynchronous process using the SystemTags() function. When the AppMenuItem has been activated five times, the program exits after freeing any system resources it has used.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	/* appmenuitem.c		/* appmenuitem.c
	/* Works from the Shell (CLI) only */		/* Works from the Shell (CLI) only */
Line 507:		Line 507:
	This example shows how to create an AppWindow and obtain arguments from Workbench when the user drops an icon into it. The AppWindow will appear on the Workbench screen with the name "AppWindow" and will run until the window's close gadget is selected. If any icons are dropped into the AppWindow, the program prints their arguments in the Shell window.		This example shows how to create an AppWindow and obtain arguments from Workbench when the user drops an icon into it. The AppWindow will appear on the Workbench screen with the name "AppWindow" and will run until the window's close gadget is selected. If any icons are dropped into the AppWindow, the program prints their arguments in the Shell window.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	/* appwindow.c */		/* appwindow.c */
	/* Works from the Shell (CLI) only */		/* Works from the Shell (CLI) only */

Frédéric Khannouf: /* An AppIcon Example */ Typo fix

2024-02-19T10:00:51Z

An AppIcon Example: Typo fix

← Older revision		Revision as of 10:00, 19 February 2024
Line 401:		Line 401:

	IExec->CloseLibrary(WorkbenchBase);		IExec->CloseLibrary(WorkbenchBase);
	~~IEec~~->CloseLibrary(IconBase);		IExec->CloseLibrary(IconBase);

	return 0;		return 0;

Brian Deneen: /* The Info File */ Moved the sentence starting with "The icon type can be set. . ." from the end of the paragraph to the beginning. It is the topic sentence, not the conclusion.

2016-05-18T16:43:21Z

The Info File: Moved the sentence starting with "The icon type can be set. . ." from the end of the paragraph to the beginning. It is the topic sentence, not the conclusion.

← Older revision		Revision as of 16:43, 18 May 2016
Line 33:		Line 33:
	Icons can be created with the IconEdit program (in the Tools directory of the Extras disk), or by copying an existing ''.info'' file of the correct type. Icons can also be created under program control with PutDiskObject(). See [[Icon Library]] for a discussion of the icon library functions.		Icons can be created with the IconEdit program (in the Tools directory of the Extras disk), or by copying an existing ''.info'' file of the correct type. Icons can also be created under program control with PutDiskObject(). See [[Icon Library]] for a discussion of the icon library functions.

	For an executable file the icon type must be set to tool. For a data file the icon type must be set to project. Create icons for your application disk and directories too. For a directory, the icon is stored in a ''.info'' file at the same level where the directory name appears (not in the directory itself). The icon type should be set to drawer. The icon for a disk should always be stored in a file named ''disk.info'' at the root level directory of the disk. The icon type should be set to disk. ~~(The icon type can be set and the icon imagery edited with the IconEdit program.)~~		'''The icon type can be set and the icon imagery edited with the IconEdit program.''' For an executable file the icon type must be set to tool. For a data file the icon type must be set to project. Create icons for your application disk and directories too. For a directory, the icon is stored in a ''.info'' file at the same level where the directory name appears (not in the directory itself). The icon type should be set to drawer. The icon for a disk should always be stored in a file named ''disk.info'' at the root level directory of the disk. The icon type should be set to disk.

	== Workbench Environment ==		== Workbench Environment ==

Steven Solie: /* Workbench Library */

2015-11-03T20:43:35Z

Workbench Library

← Older revision		Revision as of 20:43, 3 November 2015
Line 1:		Line 1:
	== Workbench Library ==		== Workbench Library ==

	Workbench is the graphic user interface to the Amiga file system that uses symbols called icons to represent disks, directories and files. This ~~chapter~~ shows how to use workbench.library.		Workbench is the graphic user interface to the Amiga file system that uses symbols called icons to represent disks, directories and files. This article shows how to use workbench.library.

	Workbench is both a system program and a screen. Normally it is the first thing the user sees when the machine is booted providing a friendly operating environment for launching applications and performing other important system activities like navigating through the Amiga's hierarchical filing system.		Workbench is both a system program and a screen. Normally it is the first thing the user sees when the machine is booted providing a friendly operating environment for launching applications and performing other important system activities like navigating through the Amiga's hierarchical filing system.

Steven Solie: /* The AppMessage Structure */

2015-07-22T23:31:53Z

The AppMessage Structure

← Older revision		Revision as of 23:31, 22 July 2015
Line 257:		Line 257:

	The AppMessage's am_Type field tells the application which type of AppObject the message is about. The field will be:		The AppMessage's am_Type field tells the application which type of AppObject the message is about. The field will be:
	* ~~MTYPE_APPWINDOW~~ if the message is about an AppWindow,		* AMTYPE_APPWINDOW if the message is about an AppWindow,
	* ~~MTYPE_APPICON~~ if the message is about an AppIcon, or		* AMTYPE_APPICON if the message is about an AppIcon, or
	* ~~MTYPE_APPMENUITEM~~ if the message is about an AppMenuItem.		* AMTYPE_APPMENUITEM if the message is about an AppMenuItem.

	When an application creates an AppObject, it can assign the AppObject application specific data (most likely a pointer) and an ID. Workbench will pass an AppObject's data and ID back to the application when it sends an AppMessage about the AppObject. The AppMessage's am_UserData and am_ID fields hold the user data and the ID.		When an application creates an AppObject, it can assign the AppObject application specific data (most likely a pointer) and an ID. Workbench will pass an AppObject's data and ID back to the application when it sends an AppMessage about the AppObject. The AppMessage's am_UserData and am_ID fields hold the user data and the ID.

Steven Solie at 19:39, 17 March 2014

2014-03-17T19:39:27Z

← Older revision		Revision as of 19:39, 17 March 2014
Line 31:		Line 31:
	\|}		\|}

	Icons can be created with the IconEdit program (in the Tools directory of the Extras disk), or by copying an existing ''.info'' file of the correct type. Icons can also be created under program control with PutDiskObject(). See ~~the~~ discussion of the icon library functions ~~below for more on this~~.		Icons can be created with the IconEdit program (in the Tools directory of the Extras disk), or by copying an existing ''.info'' file of the correct type. Icons can also be created under program control with PutDiskObject(). See [[Icon Library]] for a discussion of the icon library functions.

	For an executable file the icon type must be set to tool. For a data file the icon type must be set to project. Create icons for your application disk and directories too. For a directory, the icon is stored in a ''.info'' file at the same level where the directory name appears (not in the directory itself). The icon type should be set to drawer. The icon for a disk should always be stored in a file named ''disk.info'' at the root level directory of the disk. The icon type should be set to disk. (The icon type can be set and the icon imagery edited with the IconEdit program.)		For an executable file the icon type must be set to tool. For a data file the icon type must be set to project. Create icons for your application disk and directories too. For a directory, the icon is stored in a ''.info'' file at the same level where the directory name appears (not in the directory itself). The icon type should be set to drawer. The icon for a disk should always be stored in a file named ''disk.info'' at the root level directory of the disk. The icon type should be set to disk. (The icon type can be set and the icon imagery edited with the IconEdit program.)

Steven Solie: /* Workbench and Icon Library */

2014-03-17T19:37:00Z

Workbench and Icon Library

← Older revision		Revision as of 19:37, 17 March 2014
Line 1:		Line 1:
	== Workbench ~~and Icon~~ Library ==		== Workbench Library ==

	Workbench is the graphic user interface to the Amiga file system that uses symbols called icons to represent disks, directories and files. This chapter shows how to use ~~Workbench and its two support libraries~~ workbench~~.library and icon~~.library.		Workbench is the graphic user interface to the Amiga file system that uses symbols called icons to represent disks, directories and files. This chapter shows how to use workbench.library.

	Workbench is both a system program and a screen. Normally it is the first thing the user sees when the machine is booted providing a friendly operating environment for launching applications and performing other important system activities like navigating through the Amiga's hierarchical filing system.		Workbench is both a system program and a screen. Normally it is the first thing the user sees when the machine is booted providing a friendly operating environment for launching applications and performing other important system activities like navigating through the Amiga's hierarchical filing system.

Steven Solie: Steven Solie moved page Workbench and Icon Library to Workbench Library without leaving a redirect: Split into two sections

2014-03-17T19:36:01Z

Steven Solie moved page Workbench and Icon Library to Workbench Library without leaving a redirect: Split into two sections

← Older revision	Revision as of 19:36, 17 March 2014
(No difference)

Steven Solie: /* Function Reference */

2014-03-17T19:34:36Z

Function Reference

@@ Line 665: / Line 665: @@
 == Function Reference ==
-The following are brief descriptions of the functions in workbench.library and icon.library. See SDK for details on each function call.
+The following are brief descriptions of the functions in workbench.library. See SDK for details on each function call.
 {| class="wikitable"

Steven Solie: /* The Icon Library */

2014-03-17T19:33:33Z

The Icon Library

Show changes