amiga | Various utilities for reviving your amiga

Variables in PowerShell are scoped, and defaults to the current local scope, ie. the function body. The AllScope option does not make it available to antecedent scopes, it simply ensures PowerShell copies the variable into any new child scope created from the current scope.

To make the variable available in the parent scope, use -Scope 1 when calling New-Variable:

It looks like you want the data sorted overall. You haven't specified your database, but this would work in most databases:

I found a solution:

"I want to create the smallest possible size bitmap of the characters. (The "original" size in pixels). More accurately, the characters' smallest possible size."

"...maybe there is a way to extract the original pixel ratio of the characters from a .ttf?"

One way of extracting the original pixel height is the website: fontdrop.info.

Drag the .ttf file over and select "Data" panel. And scroll down to you see:

That would be the pixel height (of the tallest glyph). And when when using this (16) as the font-size parameter, gave me the original size.

Short description:

According to the specification the upper byte represents the OS which created the ZIP file. The lower byte is the version of the used ZIP specification.

In your example:

788 = 0x0314

OS which created the ZIP file:
0x03 (Upper Byte): UNIX

4.4.2.1 The upper byte indicates the compatibility of the file attribute information. If the external file attributes are compatible with MS-DOS and can be read by PKZIP for DOS version 2.04g then this value will be zero. If these attributes are not compatible, then this value will identify the host system on which the attributes are compatible. Software can use this information to determine the line record format for text files etc.

ZIP specification version:
0x14 (Lower Byte): Version 2.0

0x14 / 10 = 2 (Major version number)
0x14 % 10 = 0 (Minor version number)

4.4.2.3 The lower byte indicates the ZIP specification version (the version of this document) supported by the software used to encode the file. The value/10 indicates the major version number, and the value mod 10 is the minor version number.

For Windows NTFS, the correct "version made by" value should be:

0x0A14 = 2580

0x0A (Upper Byte): Windows NTFS (Win32)
0x14 (Lower Byte): Version 2.0

Extract from adm-zip source:

This should work;

There are different ways of doing this.

Here's a solution that involves using float:left style for your table:

PRIMARY keys must be unique. So when you replace with (111, 'IOS') it replaces any existing entry with user_id = 111, hence you end up with only (111, 'IOS') in the table. If you want to insert all the values, you need to remove the PRIMARY KEY on user_id (perhaps replace it with an index). For example:

I'd guess you'd want to write a macro that you can use like AUTONUMBER s_id STATUS_OKAY that takes two args: 2nd is the symbol name to define, 1st is the counter to increment.

You'd want it to expand to something like: