Free Pascal wiki - Recent changes [en]

FPSpreadsheet: Chart Tutorial

2025-05-26T09:26:21Z

Changing the series fill pattern

← Older revision		Revision as of 11:26, 26 May 2025
(2 intermediate revisions by the same user not shown)
Line 126:		Line 126:

	=== Filling chart elements ===		=== Filling chart elements ===
	Now let's modify the appearance of the series bars (property <tt>series.Fill</tt>) and of the chart background (property <tt>chart.Background</tt>). Both are of ~~tyoe~~ <tt>TsChartFill</tt> which gives access to all properties related to filling: fill style, fill color, ~~hatch~~ parameters, gradient parameters:		Now let's modify the appearance of the series bars (property <tt>series.Fill</tt>) and of the chart background (property <tt>chart.Background</tt>). Both are of type <tt>TsChartFill</tt> which gives access to all properties related to filling: fill style, fill color, pattern parameters, gradient parameters:
	<syntaxhighlight lang="pascal">		<syntaxhighlight lang="pascal">
	type		type
Line 136:		Line 136:
	Color: TsChartColor;		Color: TsChartColor;
	Gradient: Integer; // Index into chart's Gradients list		Gradient: Integer; // Index into chart's Gradients list
	~~Hatch~~: Integer; // Index into chart's ~~Hatches~~ list		Pattern: Integer; // Index into chart's FillPattern list
	Image: Integer; // Index into chart's Images list		Image: Integer; // Index into chart's Images list
	[...]		[...]
Line 146:		Line 146:
	type		type
	TsChartColor = record		TsChartColor = record
	Transparency: ~~single~~; // 0.0 (opaque) ... 1.0 (transparent)		Transparency: TsChartTransparency; // = single in the range 0.0 (opaque) ... 1.0 (transparent)
	case Integer of		case Integer of
	0: (Red, Green, Blue, SystemColorIndex: Byte);		0: (Red, Green, Blue, SystemColorIndex: Byte);
Line 163:		Line 163:
	</syntaxhighlight>		</syntaxhighlight>

	==== Changing the series color ====		==== Changing the series fill color ====
	At first we change the color of the 1st series bars to some brighter blue, and its border to black:		At first we change the color of the 1st series bars to some brighter blue, and its border to black:

	<syntaxhighlight lang="pascal">		<syntaxhighlight lang="pascal">
	ser1.Fill.Color := ChartColor($FFAA88); // bright blue fill of the bars		ser1.Fill.Color := ChartColor($FFAA88); // bright blue fill of the bars
	ser1.Line.Color := ChartColor(scBlack); // ~~black border~~ of the ~~bars~~; ~~ser1~~.Line ~~is of type TsChartLine~~		ser1.Fill.Style := cfsSolidFill;
			</syntaxhighlight>

			==== Changing the series fill pattern ====
			The 2nd bar series is supposed to be hatched by a pattern of diagonal-up strokes. The library provides a lot of pre-defined fill patterns which can be identified by the <tt>TsChartFillPatternStyle</tt> enumeration (declared in unit ''fpsTypes''):
			<syntaxhighlight lang="pascal">
			type
			TsChartFillPatternStyle = (
			fpsGray05, fpsGray10, fpsGray20, fpsGray25, fpsGray30, fpsGray40,
			fpsGray50, fpsGray60, fpsGray70, fpsGray75, fpsGray80, fpsGray90,
			fpsHorThick, fpsVertThick, fpsDiagUpThick, fpsDiagDownThick, fpsHatchThick, fpsCrossThick,
			fpsHorThin, fpsVertThin, fpsDiagUpThin, fpsDiagDownThin, fpsHatchThin, fpsCrossThin,
			fpsHorNarrow, fpsVertNarrow, fpsDiagUpNarrow, fpsDiagDownNarrow, fpsHatchNarrow, fpsCrossNarrow,
			fpsHorDash, fpsVertDash, fpsDiagUpDash, fpsDiagDownDash, fpsHatchDot, fpsCrossDot,
			fpsBrickDiag, fpsBrickHor, fpsCheckerBoardLarge, fpsCheckerBoardSmall, fpsConfettiLarge, fpsConfettiSmall,
			fpsDiamond, fpsDivot, fpsPlaid, fpsShingle, fpsSphere, fpsTrellis, fpsWave, fpsWeave, fpsZigZag
			);
			</syntaxhighlight>
			There are several "diagonal-up" patterns, a nice one is <tt>fpsDiagUpNarrow</tt>. In order to fill an area, such as the series bars, by it, we must add the combination of fill pattern style, foreground and background color to the chart's <tt>FillPatterns</tt> list (<tt>Chart.FillPatterns.AddPattern(name, style, forgroundColor, backgroundColor)</tt>. This process returns the index of this colored pattern in this list which is needed as the <tt>Pattern</tt> index of the <tt>TsChartFill</tt> class. If this index is already known from a previous fill, of course, you can reuse it instead.

			<syntaxhighlight lang="pascal">
			ser2.Fill.Pattern := wchart.FillPatterns.AddPattern('white-on-blue diag-up', fpsDiagUpNarrow, ChartColor(scWhite), ChartColor(scBlue));
			// Drop the last argument if you need a pattern without background
			ser2.Fill.Style := cfsPattern;
			ser2.Line.Color := ChartColor(scBlack);
			</syntaxhighlight>

			Alternatively you can also fill the area by any bitmap loaded from file: Add the bitmap file to the workbook's embedded object list (<tt>workbook.AddEmbeddedObj(filename)</tt>) and then use the returned index in the method <tt>AddImage</tt> of the chart's <tt>Images</tt> list:
			<syntaxhighlight lang="pascal">
			ser2.Fill.Image := wchart.Images.AddImage('FillImg', wbook.AddEmbeddedObj('bgimage.jpg'));
			ser2.Fill.Style := cfsImage;
			ser2.Line.Color := ChartColor(scBlack);
	</syntaxhighlight>		</syntaxhighlight>

CudaText

2025-05-24T16:37:39Z

fmt the topic 'command line'

← Older revision	Revision as of 18:37, 24 May 2025
(One intermediate revision by the same user not shown)
(No difference)

IDE Window: Environment Options

2025-05-23T18:39:44Z

Added section for "Messages Window" frame (no content yet)

← Older revision		Revision as of 20:39, 23 May 2025
(One intermediate revision by the same user not shown)
Line 175:		Line 175:
	* Show gutter		* Show gutter
	* Draw grid lines		* Draw grid lines
			<br clear="all">

			== Messages Window ==

			Options for the Messages window.
	<br clear="all">		<br clear="all">

Line 182:		Line 187:

	Contains paths to FPDoc files with documentation for the units not documented in a project. You can also add paths to the RTL's (*.xml) documentations files, so that tooltip help works for both RTL code.		Contains paths to FPDoc files with documentation for the units not documented in a project. You can also add paths to the RTL's (*.xml) documentations files, so that tooltip help works for both RTL code.
			<br clear="all">

			== IDE Startup ==

			The section that controls the IDE startup settings.
	<br clear="all">		<br clear="all">

User:Secordrian

2025-05-23T11:02:55Z

User account Secordrian was created

Character and string types

2025-05-23T06:51:31Z

← Older revision		Revision as of 08:51, 23 May 2025
Line 322:		Line 322:

	The rules for conversion are laid out in a [https://freepascal.org/docs-html/ref/refsu9.html#x32-380003.2.4 "Code page conversions"] section in the FPC manual. The basic point is that assigning an AnsiString (including the <tt>CP_UTF8</tt> specialization) to another AnsiString converts what is in the source to match the code page of the target string. A quirk for compatibility with presumably fpc ≤ 2.6.5 is that no such conversion will be done if one matches the source code CP and the other matches the system CP. In this case, forced (likely incorrect) interpretation as the target code page will occur.		The rules for conversion are laid out in a [https://freepascal.org/docs-html/ref/refsu9.html#x32-380003.2.4 "Code page conversions"] section in the FPC manual. The basic point is that assigning an AnsiString (including the <tt>CP_UTF8</tt> specialization) to another AnsiString converts what is in the source to match the code page of the target string. A quirk for compatibility with presumably fpc ≤ 2.6.5 is that no such conversion will be done if one matches the source code CP and the other matches the system CP. In this case, forced (likely incorrect) interpretation as the target code page will occur.

			== Conversions ==
			=== Ascii code to string ===
			The examples below will convert $48 to 'H':
			<syntaxhighlight lang="pascal">
			String(char($48))
			</syntaxhighlight>
			or
			<syntaxhighlight lang="pascal">
			String(#$48)
			</syntaxhighlight>

	== See also ==		== See also ==

User:HaraldNieswandt

2025-05-21T13:30:35Z

User account HaraldNieswandt was created

RichMemo

2025-05-21T06:10:01Z

CaretPos

← Older revision		Revision as of 08:10, 21 May 2025
(3 intermediate revisions by the same user not shown)
Line 384:		Line 384:

	So right now, you might run into an issue, If you create a project in Gtk2 and save the richmemo is design time containing Unicode characters. Then if you try to load it on the XP machine and would use widgetset native loader, you might see characters missing or rendered improperly. Changing to the usage of RichMemo RTF loader/saver will prevent this issue from happening. Currently you can also avoid it by registering RichMemo loaders (call RegisterRTFLoader, RegisterRTFSaver procedures in project initialization, before any RichMemo is loaded)		So right now, you might run into an issue, If you create a project in Gtk2 and save the richmemo is design time containing Unicode characters. Then if you try to load it on the XP machine and would use widgetset native loader, you might see characters missing or rendered improperly. Changing to the usage of RichMemo RTF loader/saver will prevent this issue from happening. Currently you can also avoid it by registering RichMemo loaders (call RegisterRTFLoader, RegisterRTFSaver procedures in project initialization, before any RichMemo is loaded)

			=== CaretPos ===
			Read/Write property. Gets or sets the positon of the caret in the memo.
			<source lang="delphi">
			property CaretPos: TPoint;
			</source>

			For example, to get the line of the caret use
			<source lang="delphi">
			RichMemo1.CaretPos.Y;
			</source>

			For example, to move the caret to line 5, character 10 use
			<source lang="delphi">
			RichMemo1.CaretPos := Point(10,5);
			RichMemo1.SetFocus;
			</source>

	==Events==		==Events==