Graphics Primitives - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:08:16Z

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

Steven Solie: /* Copying Rectangular Areas */

2015-11-06T17:52:06Z

Copying Rectangular Areas

← Older revision		Revision as of 17:52, 6 November 2015
Line 783:		Line 783:
	The source bitmap is specified by the &srcBM argument. The position of the source area within the bitmap is specified by srcX and srcY. The destination bitmap is specified by the &dstBM argument. The position of the destination area within the bitmap is specified by dstX and dstY.		The source bitmap is specified by the &srcBM argument. The position of the source area within the bitmap is specified by srcX and srcY. The destination bitmap is specified by the &dstBM argument. The position of the destination area within the bitmap is specified by dstX and dstY.

	The dimensions (in pixels) of the area to be moved is indicated by the sizeX and sizeY arguments. With the original custom chip set, the blitter size limits are ~~992x1~~,024. With ECS the blitter size limits are 32,~~736x32~~,768. See the section on ~~“Determining~~ Chip ~~Versions” earlier in this chapter~~ to find out how to tell if the host system has ECS installed.		The dimensions (in pixels) of the area to be moved is indicated by the sizeX and sizeY arguments. With the original custom chip set, the blitter size limits are 992 x 1,024. With ECS the blitter size limits are 32,736 x 32,768. See the section on [[Classic_Graphics_Primitives#Determining_Chip_Versions\|Determining Chip Versions]] to find out how to tell if the host system has ECS installed.

	The minterm argument determines what logical operation to perform on the rectangle data as bits are moved (described above). The mask argument, normally set to 0xff, specifies which bitplanes will be involved in the blit operation and which will be ignored. If a bit is set in the mask byte, the corresponding bitplane is included. The tempA argument applies only to blits that overlap and, if non-NULL, points to Chip memory the system will use for temporary storage during the blit.		The minterm argument determines what logical operation to perform on the rectangle data as bits are moved (described above). The mask argument, normally set to 0xff, specifies which bitplanes will be involved in the blit operation and which will be ignored. If a bit is set in the mask byte, the corresponding bitplane is included. The tempA argument applies only to blits that overlap and, if non-NULL, points to Chip memory the system will use for temporary storage during the blit.

Steven Solie: /* Graphics Primitives */

2015-11-06T17:49:21Z

Graphics Primitives

← Older revision		Revision as of 17:49, 6 November 2015
Line 2:		Line 2:
	== Graphics Primitives ==		== Graphics Primitives ==

	This article describes the basic graphics functions available to Amiga programmers. It covers the graphics support structures, display routines and drawing routines. Many of the operations described in this section are also performed by the Intuition software. See the Intuition ~~chapters~~ for more information.		This article describes the basic graphics functions available to Amiga programmers. It covers the graphics support structures, display routines and drawing routines. Many of the operations described in this section are also performed by the Intuition software. See the Intuition articles for more information.

	The Amiga supports several basic types of graphics routines: display routines, drawing routines, sprites and animation. These routines are very versatile and allow you to define any combination of drawing and display areas you may wish to use.		The Amiga supports several basic types of graphics routines: display routines, drawing routines, sprites and animation. These routines are very versatile and allow you to define any combination of drawing and display areas you may wish to use.

Steven Solie: /* Using the Graphics Drawing Routines */

2015-11-06T17:48:55Z

Using the Graphics Drawing Routines

← Older revision		Revision as of 17:48, 6 November 2015
Line 341:		Line 341:
	=== Using the Graphics Drawing Routines ===		=== Using the Graphics Drawing Routines ===

	This section shows you how to use the Amiga drawing routines. All of these routines work either on their own or along with the windowing system and layers library. For details about using the layers and windows, see ~~the~~ ~~chapters on “Layers Library”~~ and ~~“Intuition~~ ~~Windows”~~.		This section shows you how to use the Amiga drawing routines. All of these routines work either on their own or along with the windowing system and layers library. For details about using the layers and windows, see [[Layers Library]] and [[Intuition Windows]].

	{{Note\|title=Use WaitBlit()\|text=The graphics library rendering and data movement routines generally wait to get access to the blitter, start their blit, and then exit. Therefore, you must WaitBlit() after a graphics rendering or data movement call if you intend to immediately deallocate, examine, or perform order-dependent processor operations on the memory used in the call.}}		{{Note\|title=Use WaitBlit()\|text=The graphics library rendering and data movement routines generally wait to get access to the blitter, start their blit, and then exit. Therefore, you must WaitBlit() after a graphics rendering or data movement call if you intend to immediately deallocate, examine, or perform order-dependent processor operations on the memory used in the call.}}

Steven Solie: /* Graphics Primitives */

2015-11-06T17:48:15Z

Graphics Primitives

← Older revision		Revision as of 17:48, 6 November 2015
Line 2:		Line 2:
	== Graphics Primitives ==		== Graphics Primitives ==

	This ~~chapter~~ describes the basic graphics functions available to Amiga programmers. It covers the graphics support structures, display routines and drawing routines. Many of the operations described in this section are also performed by the Intuition software. See the Intuition chapters for more information.		This article describes the basic graphics functions available to Amiga programmers. It covers the graphics support structures, display routines and drawing routines. Many of the operations described in this section are also performed by the Intuition software. See the Intuition chapters for more information.

	The Amiga supports several basic types of graphics routines: display routines, drawing routines, sprites and animation. These routines are very versatile and allow you to define any combination of drawing and display areas you may wish to use.		The Amiga supports several basic types of graphics routines: display routines, drawing routines, sprites and animation. These routines are very versatile and allow you to define any combination of drawing and display areas you may wish to use.

Steven Solie: /* Text Attributes */

2015-11-06T17:48:05Z

Text Attributes

← Older revision		Revision as of 17:48, 6 November 2015
Line 314:		Line 314:
	==== Text Attributes ====		==== Text Attributes ====

	Text attributes and font information are stored in the RastPort fields Font, AlgoStyle, TxFlags, TxHeight, TxWidth, TxBaseline and TxSpacing. These are normally set by calls to the graphics font routines which are covered separately in ~~the chapter on “Graphics~~ Library and Text.”		Text attributes and font information are stored in the RastPort fields Font, AlgoStyle, TxFlags, TxHeight, TxWidth, TxBaseline and TxSpacing. These are normally set by calls to the graphics font routines which are covered separately in [[Graphics Library and Text]].

	==== Working with 32 bit colours on direct mapped screens ====		==== Working with 32 bit colours on direct mapped screens ====

Steven Solie: /* When to Wait for the Blitter */

2015-09-25T21:41:38Z

When to Wait for the Blitter

← Older revision		Revision as of 21:41, 25 September 2015
Line 838:		Line 838:

	<syntaxhighlight>		<syntaxhighlight>
	OwnBlitter(); /* Gain exclusive access to the hardware blitter */		IGraphics->OwnBlitter(); /* Gain exclusive access to the hardware blitter */

	for(planes=0; planes < bitmap->depth; planes++)		for(planes=0; planes < bitmap->depth; planes++)
	{		{
	WaitBlit(); /* Sleep until the previous blitter operation completes */		IGraphics->WaitBlit(); /* Sleep until the previous blitter operation completes */
	/* start a blit */		/* start a blit */
	}		}

	DisownBlitter(); /* Release exclusive access to the hardware blitter */		IGraphics->DisownBlitter(); /* Release exclusive access to the hardware blitter */
	</syntaxhighlight>		</syntaxhighlight>

Steven Solie: /* Performing Data Move Operations */

2015-09-25T21:36:32Z

Performing Data Move Operations

Show changes

Steven Solie: /* Rectangle-fill Operations */

2015-09-25T21:25:49Z

Rectangle-fill Operations

← Older revision		Revision as of 21:25, 25 September 2015
Line 577:		Line 577:
	The final fill function, RectFill(), is for filling rectangular areas. The form of this function follows:		The final fill function, RectFill(), is for filling rectangular areas. The form of this function follows:

			<syntaxhighlight>
	<pre>
	RectFill(&~~amp;~~rastPort, xmin, ymin, xmax, ymax);		RectFill(&rastPort, xmin, ymin, xmax, ymax);
			</syntaxhighlight>
	</pre>

	As usual, the rastPort argument specifies the RastPort you want to draw into. The xmin and ymin arguments specify the upper left corner of the rectangle to be filled. The xmax and ymax arguments specify the lower right corner of the rectangle to be filled. Note that the variable xmax must be equal to or greater than xmin, and ymax must be equal to or greater than ymin.		As usual, the rastPort argument specifies the RastPort you want to draw into. The xmin and ymin arguments specify the upper left corner of the rectangle to be filled. The xmax and ymax arguments specify the lower right corner of the rectangle to be filled. Note that the variable xmax must be equal to or greater than xmin, and ymax must be equal to or greater than ymin.

Steven Solie: /* Drawing Multiple Lines with a Single Command */

2015-09-25T21:23:08Z

Drawing Multiple Lines with a Single Command

← Older revision		Revision as of 21:23, 25 September 2015
Line 447:		Line 447:

	<syntaxhighlight>		<syntaxhighlight>
	PolyDraw(&~~amp;~~rastPort, count, arraypointer);		PolyDraw(&rastPort, count, arraypointer);
	</syntaxhighlight>		</syntaxhighlight>