Offset path in Affinity Designer for iPad – Padcrafting.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
replace.me › en-us › designer. Effortlessly add a contour to any object or increase the width of single open curves. It’s an easy way to create abstract shapes or an offset path — great for.
 
 

Affinity Designer for iPad – Take Your Designs Further.Affinity Designer – Professional Graphic Design Software

 
The 1.

 

Affinity designer offset tool free.Let’s get technical

 

This translation can take the form of the addition or subtraction of an offset. The address the processor places on the processor bus will be known here as the processor-relative address. Unless otherwise noted, all addresses used within this section are processor-relative addresses. For example, consider a platform with two root PCI buses.

The platform designer has several choices. Industry standard PCs do not provide address space translations because of historical compatibility issues. System Description Table Header.

All numeric values in ACPI-defined tables, blocks, and structures are always encoded in little endian format. Signature values are stored as fixed-length strings. For future expansion, all data items marked as reserved in this specification have strict meanings. This section lists software requirements for reserved fields.

OEM implementations of software and AML code return only defined values and do not return reserved values. Software preserves the value of all reserved bits in hardware control registers by writing back read values.

Software handles ignored bits in ACPI hardware registers the same way it handles reserved bits in these same types of registers. All versions of the ACPI tables must maintain backward compatibility. To accomplish this, modifications of the tables consist of redefinition of previously reserved fields and values plus appending data to the 1. Modifications of the ACPI tables require that the version numbers of the modified tables be incremented.

The length field in the tables includes all additions and the checksum is maintained for the entire length of the table. Addresses used in the ACPI 1. This was targeted at the IA environment.

Newer architectures require addressing mechanisms beyond that defined in ACPI 1. ACPI defines the fixed hardware low-level interfaces as a means to convey to the system OEM the minimum interfaces necessary to achieve a level of capability and quality for motherboard configuration and system power management.

Additionally, the definition of these interfaces, as well as others defined in this specification, conveys to OS Vendors OSVs developing ACPI-compatible operating systems, the necessary interfaces that operating systems must manipulate to provide robust support for system configuration and power management.

While the definition of low-level hardware interfaces defined by ACPI 1. Unfortunately, the nature of SMM-based code makes this type of OS independent implementation difficult if not impossible to debug. As such, this implementation approach is not recommended. In some cases, Functional Fixed Hardware implementations may require coordination with other OS components.

As such, an OS independent implementation may not be viable. OS-specific implementations of functional fixed hardware can be implemented using technical information supplied by the CPU manufacturer. The downside of this approach is that functional fixed hardware support must be developed for each OS. In some cases, the CPU manufacturer may provide a software component providing this support. In other cases support for the functional fixed hardware may be developed directly by the OS vendor.

The hardware register definition was expanded, in ACPI 2. This is accomplished through the specification of an address space ID in the register definition see Generic Address Structure for more information. When specifically directed by the CPU manufacturer, the system firmware may define an interface as functional fixed hardware by indicating 0x7F Functional Fixed Hardware , in the address space ID field for register definitions.

It is emphasized that functional fixed hardware definitions may be declared in the ACPI system firmware only as indicated by the CPU Manufacturer for specific interfaces as the use of functional fixed hardware requires specific coordination with the OS vendor.

Only certain ACPI-defined interfaces may be implemented using functional fixed hardware and only when the interfaces are common across machine designs for example, systems sharing a common CPU architecture that does not support fixed hardware implementation of an ACPI-defined interface. OEMs are cautioned not to anticipate that functional fixed hardware support will be provided by OSPM differently on a system-by-system basis.

The use of functional fixed hardware carries with it a reliance on OS specific software that must be considered. OEMs should consult OS vendors to ensure that specific functional fixed hardware interfaces are supported by specific operating systems. The size in bits of the given register. When addressing a data structure, this field must be zero. The bit offset of the given register at the given address.

The bit address of the data structure or register in the given address space relative to the processor. See below for specific formats. The bit physical memory address relative to the processor of the register. This can also be found as part of the DCE 1. This is the checksum of the fields defined in the ACPI 1. This includes only the first 20 bytes of this table, bytes 0 to 19, including the checksum field. These bytes must sum to zero. The revision of this structure. Larger revision numbers are backward compatible to lower revision numbers.

The ACPI version 1. It does not include the Length field and beyond. The current value for this field is 2. The length of the table, in bytes, including the header, starting from offset 0. This field is used to record the size of the entire table. This field is not available in the ACPI version 1. The Signature field in this table determines the content of the system description table.

The revision of the structure corresponding to the signature field for this table. Larger revision numbers are backward compatible to lower revision numbers with the same signature. This field is particularly useful when defining a definition block to distinguish definition block functions. Vendor ID of utility that created the table. Revision of utility that created the table. The intent of these fields is to allow for a binary control system that support services can use. Because many support functions can be automated, it is useful when a tool can programmatically determine which table release is a compatible and more recent revision of a prior table on the same OEMID and OEM Table ID.

Table 5. These system description tables may be defined by ACPI and documented within this specification, or they may simply be reserved by ACPI and defined by other industry specifications. For tables defined by other industry specifications, the ACPI specification acts as gatekeeper to avoid collisions in table signatures.

Requests to reserve a 4-byte alphanumeric table signature should be sent to the email address info acpi. Tables defined outside of the ACPI specification may define data value encodings in either little endian or big endian format. For the purpose of clarity, external table definition documents should include the endian-ness of their data value encodings. Section 5. Section Arm Error Source Table. Component Distance Information Table.

Component Resource Attribute Table. Core System Resource Table. Debug Port Table. Debug Port Table 2. DMA Remapping Table. Dynamic Root of Trust for Measurement Table. Event Timer Description Table Obsolete. Low Power Idle Table. Management Controller Host Interface table. Arm Memory Partitioning And Monitoring. Microsoft Data Management Table. Platform Runtime Mechanism Table.

Regulatory Graphics Resource Table. Software Delegated Exceptions Interface. Microsoft Software Licensing table. Microsoft Serial Port Console Redirection table.

Server Platform Management Interface table. Trusted Platform Module 2 Table. Unified Extensible Firmware Interface Specification. Watch Dog Action Table. Watchdog Resource Table. Windows Platform Binary Table. Windows Security Mitigations Table. Xen Project. OSPM examines each table for a known signature.

Based on the signature, OSPM can then interpret the implementation-specific data within the table. Length, in bytes, of the entire RSDT. The length implies the number of Entry fields n at the end of the table. Length, in bytes, of the entire table. All fields in the FADT that provide hardware addresses provide processor-relative physical addresses.

In this case, the bit field must be ignored regardless of whether or not it is zero, and whether or not it is the same value as the bit field. The bit field should only be used if the corresponding bit field contains a zero value, or if the bit value can not be used by the OSPM subject to e.

CPU addressing limitations. This signature predates ACPI 1. See Section 5. Physical memory address of the DSDT. ACPI 1. Platforms should set this field to zero but field values of one are also allowed to maintain compatibility with ACPI 1. System vector the SCI interrupt is wired to in mode. On systems that do not contain the , this field contains the Global System interrupt number of the SCI interrupt. This field is reserved and must be zero on system that does not support System Management mode.

This field is reserved and must be zero on systems that do not support Legacy Mode. The S4BIOS state provides an alternate way to enter the S4 state where the firmware saves and restores the memory context.

See Section 4. This is a required field. This field is optional; if this register block is not supported, this field contains zero. See Table 4.

See the Section 4. This is an optional field; if this register block is not supported, this field contains zero. If this register block is not supported, this field contains zero. Support for the PM2 register block is optional.

If not supported, this field contains zero. The worst-case hardware latency, in microseconds, to enter and exit a C2 state. The worst-case hardware latency, in microseconds, to enter and exit a C3 state.

This value is typically at least 2 times the cache size. This field is maintained for ACPI 1. If this field contains a zero, then the RTC day of the month alarm feature is not supported. If this field contains a zero, then the RTC month of the year alarm feature is not supported. If this field contains a zero, then the RTC centenary feature is not supported. See Table 5. Fixed feature flags. Extended physical address of the FACS. Extended physical address of the DSDT.

The address of the Sleep status register, represented in Generic Address Structure format see Section 4. All bytes in this field are considered part of the vendor identity. These identifiers are defined independently by the vendors themselves, usually following the name of the hypervisor product. Version information can be communicated through a supplemental vendor-specific hypervisor API. Firmware implementers would place zero bytes into this field, denoting that no hypervisor is present in the actual firmware.

If set, signifies that the WBINVD instruction correctly flushes the processor caches, maintains memory coherency, and upon completion of the instruction, all caches for the current processor contain no cached data other than what OSPM references and allows to be cached. If set, indicates that the hardware flushes all caches on the WBINVD instruction and maintains memory coherency, but does not guarantee the caches are invalidated.

This provides the complete semantics of the WBINVD instruction, and provides enough to support the system sleeping states. A zero indicates that the C2 power state is configured to only work on a uniprocessor UP system. A zero indicates the power button is handled as a fixed feature programming model; a one indicates the power button is handled as a control method device. Independent of the value of this field, the presence of a power button device in the namespace indicates to OSPM that the power button is handled as a control method device.

A zero indicates the sleep button is handled as a fixed feature programming model; a one indicates the sleep button is handled as a control method device. Independent of the value of this field, the presence of a sleep button device in the namespace indicates to OSPM that the sleep button is handled as a control method device. A zero indicates the RTC wake status is supported in fixed register space; a one indicates the RTC wake status is not supported in fixed register space.

Indicates whether the RTC alarm function can wake the system from the S4 state. The RTC alarm can optionally support waking the system from the S4 state, as indicated by this value. A zero indicates that the system cannot support docking.

A one indicates that the system can support docking. Notice that this flag does not indicate whether or not a docking station is currently present; it only indicates that the system is capable of docking.

System Type Attribute. If set indicates that the system has no internal expansion capabilities and the case is sealed. A value of one indicates that OSPM should use a platform provided timer to drive any monotonically non-decreasing counters, such as OSPM performance counter services. A value of one indicates that the platform is known to have a correctly implemented ACPI power management timer.

A platform may choose to set this flag if a internal processor clock or clocks in a multi-processor configuration cannot provide consistent monotonically non-decreasing counters. Note: If a value of zero is present, OSPM may arbitrarily choose to use an internal processor clock or a platform timer clock for these operations. That is, a zero does not imply that OSPM will necessarily use the internal processor clock to generate a monotonically non-decreasing counter to the system.

Some existing systems do not reliably set this input today, and this bit allows OSPM to differentiate correctly functioning platforms from platforms with this errata. A one indicates that the platform is compatible with remote power- on. Some existing platforms do not reliably transition to S5 with wake events enabled for example, the platform may immediately generate a spurious wake event after completing the S5 transition.

This flag allows OSPM to differentiate correctly functioning platforms from platforms with this type of errata. A one indicates that all local APICs must be configured for the cluster destination model when delivering interrupts in logical mode. A one indicates that all local xAPICs must be configured for physical destination mode. If this bit is set, interrupt delivery operation in logical destination mode is undefined. A one informs OSPM that the platform is able to achieve power savings in S0 similar to or better than those typically achieved in S3.

In effect, when this bit is set it indicates that the system will achieve no power benefit by making a sleep transition to S3. Most often contains one processor. Must be connected to AC power to function. This device is used to perform work that is considered mainstream corporate or home computing for example, word processing, Internet browsing, spreadsheets, and so on.

A single-user, full-featured, portable computing device that is capable of running on batteries or other power storage devices to perform its normal functions. This device performs the same task set as a desktop. Often contains more than one processor. A multi-user, stationary computing device that frequently resides in a separate, often specially designed, room. Will almost always contain more than one processor.

This device is used to support large-scale networking, database, communications, or financial operations within a corporation or government. A multi-user, stationary computing device that frequently resides in a separate area or room in a small or home office.

May contain more than one processor. This device is generally used to support all of the networking, database, communications, and financial operations of a small office or home office.

A multi-user stationary computing device that frequently resides in a separate, often specially designed room. Will often contain more than one processor. This device is used in an environment where power savings features are willing to be sacrificed for better performance and quicker responsiveness. A full-featured, highly mobile computing device which resembles writing tablets and which users interact with primarily through a touch interface. Tablet devices typically run on battery power and are generally only plugged into AC power in order to charge.

This device performs many of the same tasks as Mobile; however battery life expectations of Tablet devices generally require more aggressive power savings especially for managing display and touch components. This set of flags is used by the OS to assist in determining assumptions about power and device management. These flags are read at boot time and are used to make decisions about power management and device settings.

These flags are used by an OS at boot time before the OS is capable of providing an operating environment suitable for parsing the ACPI namespace to determine the code paths to take during boot. For example, if there are no ISA devices, an OS could skip code that assumes the presence of these devices and their associated resources. These flags are used independently of the ACPI namespace. On other system architectures, the entire field should be set to 0. User-visible devices are devices that have end-user accessible connectors for example, LPT port , or devices for which the OS must load a device driver so that an end-user application can use a device.

If clear, the OS may assume there are no such devices and that all devices in the system can be detected exclusively via industry standard device enumeration mechanisms including the ACPI namespace. If set, indicates that the motherboard contains support for a port 60 and 64 based keyboard controller, usually implemented as an or equivalent micro-controller.

For example, the E address map reporting interface would report the region as AddressRangeReserved. For more information, see Section This value is 64 bytes or larger.

This value is calculated by the platform boot firmware on a best effort basis to indicate the base hardware configuration of the system such that different base hardware configurations can have different hardware signature values. Any change to the data in Persistent Memory itself should not be included in computing the hardware signature. OSPM uses this information in waking from an S4 state, by comparing the current hardware signature to the signature values saved in the non-volatile sleep image.

If the values are not the same, OSPM assumes that the saved non-volatile image is from a different hardware configuration and cannot be restored. The bit address field where OSPM puts its waking vector. Before transitioning the system into a global sleeping state, OSPM fills in this field with the physical memory address of an OS-specific wake function. On PCs, the wake function address is in memory below 1 MB and the control is transferred while in real mode.

If, for example, the physical address is 0x, then the BIOS must jump to real mode address 0xx This field contains the Global Lock used to synchronize access to shared hardware resources between the OSPM environment and an external controller environment for example, the SMI environment.

This lock is owned exclusively by either OSPM or the firmware at any one time. When ownership of the lock is attempted, it might be busy, in which case the requesting environment exits and waits for the signal that the lock has been released. For example, the Global Lock can be used to protect an embedded controller interface such that only OSPM or the firmware will access the embedded controller interface at any one time.

Memory address translation must be disabled The processor must have psr. For IA 32 and x64 platforms, platform firmware is required to support a 32 bit execution environment. Platform firmware can additionally support a 64 bit execution environment. Otherwise, the platform firmware creates a 32 bit execution environment.

IF set to 0 Long mode enabled Paging mode is enabled and physical memory for waking vector is identity mapped virtual address equals physical address Waking vector must be contained within one physical page Selectors are set to be flat and are otherwise not used For 32 bit execution environment: Interrupts must be disabled EFLAGS. OSPM enabled firmware control structure flags. Platform firmware must initialize this field to zero.

Indicates that the platform firmware supports a 64 bit execution environment for the waking vector. Note: this is not a pointer to the Global Lock, it is the actual memory location of the lock. By convention, this lock is used to ensure that while one environment is accessing some hardware, the other environment is not. When releasing the lock, if the pending bit in the lock is set after the lock is released, a signal is sent via an interrupt mechanism to the other environment to inform it that the lock has been released.

If non-zero is returned by the function, the caller has been granted ownership of the Global Lock and can proceed. If non-zero is returned, the caller must raise the appropriate event to the other environment to signal that the Global Lock is now free. This signal only occurs when the other environment attempted to acquire ownership while the lock was owned. Although using the Global Lock allows various hardware resources to be shared, it is important to notice that its usage when there is ownership contention could entail a significant amount of system overhead as well as waits of an indeterminate amount of time to acquire ownership of the Global Lock.

For this reason, implementations should try to design the hardware to keep the required usage of the Global Lock to a minimum. The Global Lock is required whenever a logical register in the hardware is shared.

Similarly if the entire register is shared, as the case might be for the embedded controller interface, access to the register needs to be protected under the Global Lock. The top-level organization of this information after a definition block is loaded is name-tagged in a hierarchical namespace.

As mentioned, the AML Load and LoadTable operators make it possible for a Definition Block to load other Definition Blocks, either statically or dynamically, where they in turn can either define new system attributes or, in some cases, build on prior definitions. Although this gives the hardware the ability to vary widely in implementation, it also confines it to reasonable boundaries.

In some cases, the Definition Block format can describe only specific and well-understood variances. Some AML operators perform simple functions, and others encompass complex functions.

The power of the Definition block comes from its ability to allow these operations to be glued together in numerous ways, to provide functionality to OSPM. The AML operators defined in this specification are intended to allow many useful hardware designs to be easily expressed, not to allow all hardware designs to be expressed. Existing ACPI definition block implementations may contain an inherent assumption of a bit integer width. Therefore, to maintain backwards compatibility, OSPM uses the Revision field, in the header portion of system description tables containing Definition Blocks, to determine whether integers declared within the Definition Block are to be evaluated as bit or bit values.

A Revision field value greater than or equal to 2 signifies that integers declared within the Definition Block are to be evaluated as bit values. See Section This field also sets the global integer width for the AML interpreter.

Values less than two will cause the interpreter to use bit integers and math. Values of two and greater will cause the interpreter to use full bit integers and math. There can be multiple SSDTs present. This allows the OEM to provide the base support in one table and add smaller system options in other tables. For example, the OEM might put dynamic object definitions into a secondary table such that the firmware can construct the dynamic information at boot without needing to edit the static DSDT.

The ACPI interrupt model describes all interrupts for the entire system in a uniform interrupt model implementation. The choice of the interrupt model s to support is up to the platform designer. The interrupt model cannot be dynamically changed by the system firmware; OSPM will choose which model to use and install support for that model at the time of installation. If a platform supports multiple models, an OS will install support for only one of the models; it will not mix models.

Multi-boot capability is a feature in many modern operating systems. This means that a system may have multiple operating systems or multiple instances of an OS installed at any one time. Platform designers must allow for this. Only legacy systems should continue with this usage. A list of interrupt controller structures for this implementation.

This list will contain all of the structures from Interrupt Controller Structure Types needed to support this platform. These structures are described in the following sections. A one indicates that the system also has a PC-AT-compatible dual setup. Immediately after the Flags value in the MADT is a list of interrupt controller structures that declare the interrupt features of the machine.

The first byte of each structure declares the type of that structure and the second byte declares the length of that structure. OSPM implementations may limit the number of supported processors on multi-processor platforms. OSPM executes on the boot processor to initialize the platform including other processors. To ensure that the boot processor is supported post initialization, two guidelines should be followed.

The second is that platform firmware should list the boot processor as the first processor entry in the MADT. The advent of multi-threaded processors yielded multiple logical processors executing on common processor hardware. ACPI defines logical processors in an identical manner as physical processors.

To ensure that non multi-threading aware OSPM implementations realize optimal performance on platforms containing multi-threaded processors, two guidelines should be followed. The second is that platform firmware should list the first logical processor of each of the individual multi-threaded processors in the MADT before listing any of the second logical processors. This approach should be used for all successive logical processors.

Failure of OSPM implementations and platform firmware to abide by these guidelines can result in both unpredictable and non optimal platform operation.

OSPM does not expect the information provided in this table to be updated if the processor information changes during the lifespan of an OS boot. Note that the use of the Processor declaration operator is deprecated.

See the description at the beginning of this section for more information. Local APIC flags. See the following table Table 5. If this bit is set the processor is ready for use. If this bit is clear and the Online Capable bit is set, system hardware supports enabling this processor during OS runtime. The information conveyed by this bit depends on the value of the Enabled bit. If the Enabled bit is set, this bit is reserved and must be zero.

Otherwise, if this this bit is set, system hardware supports enabling this processor during OS runtime. For more information on global system interrupts see Section 5. When OSPM supports the model, it will assume that all interrupt descriptors reporting global system interrupts correspond to IRQs. In the model all global system interrupts greater than 15 are ignored. For more information on hardware resource configuration see Section 6. Most existing APIC designs, however, will contain at least one exception to this assumption.

The Interrupt Source Override Structure is provided in order to describe these exceptions. Only those that are not identity-mapped onto the APIC interrupt inputs need be described. Interrupt Source Overrides are also necessary when an identity mapped interrupt input has a non-standard polarity.

Any source that is non-maskable will not be available for use by devices. A value of 0xFF signifies that this applies to all processors in the machine. The Global System Interrupt Base field remains unchanged but has been moved.

A new address and reserved field have been added. The use of the Processor statement is deprecated. If a platform can generate an interrupt after correcting platform errors e. Some systems may restrict the retrieval of corrected platform error information to a specific processor.

In such cases, the firmware indicates the processor that can retrieve the corrected platform error information through the Processor ID and EID fields in the structure below.

On platforms where the retrieval of corrected platform error information can be performed on any processor, the firmware indicates this capability by setting the CPEI Processor Override flag in the Platform Interrupt Source Flags field of the structure below.

It is allowed for such an entry to refer to a Global System Interrupt that is already specified by a Platform Interrupt Source Structure provided through the static MADT table, provided the value of platform interrupt source flags are identical.

Platform Interrupt Source Flags. See Platform Interrupt Source Flags for a description of this field. When a logical processor is not present, the processor local X2APIC information is either not reported or flagged as disabled.

If it is not supported by the implementation, then this field must be zero. If the platform is not presenting a GICv2 with virtualization extensions this field can be 0. Address of the GIC virtual interface control block registers. On systems supporting GICv3 and above, this field holds the bit physical address of the associated Redistributor. If all of the GIC Redistributors are in the always-on power domain, GICR structures should be used to describe the Redistributors instead, and this field must be set to 0.

Describes the relative power efficiency of the associated processor. Lower efficiency class numbers are more efficient than higher ones e. This interrupt is a level triggered PPI.

Zero if SPE is not supported by this processor. If zero, this processor is unusable, and the operating system support will not attempt to use it. The frame also includes registers to discover the set of distributor lines which may be signaled by MSIs from that frame.

A system may have multiple MSI frames, and separate frames may be defined for secure and non-secure access. This structure must only be used to describe non-secure MSI frames. SPI Count used by this frame.

SPI Base used by this frame. GICR structures should only be used when describing GIC implementations which conform to version 3 or higher of the GIC architecture and which place all Redistributors in the always-on power domain. The platform firmware publishes a multiprocessor wakeup structure to let the bootstrap processor wake up application processors with a mailbox. The mailbox is memory that the firmware reserves so that each processor can have the OS send a message to them.

During system boot, the firmware puts the application processors in a state to check the mailbox. The firmware is not allowed to modify the mailbox location when the firmware transfer the control to an OS loader. The mailbox is broken down into two 2KB sections: an OS section and a firmware section.

The OS section can only be written by OS and read by the firmware, except the command field. The application processor need clear the command to Noop 0 as the acknowledgement that the command is received. The firmware must cache the content in the mailbox which might be used later before clear the command such as WakeupVector.

Only after the command is changed to Noop 0 , the OS can send the next command. The firmware section must be considered read-only to the OS and is only to be written to by the firmware.

All data communication between the OS and FW must be in little endian format. Edit one and the rest update instantly. Get a live pixel preview of your work so you know exactly how your vectors will export in raster format.

Or switch to outline view to see all those beautiful curves. Enjoy full text capabilities, including OpenType and text styles. You can flow text along any curve too. Fully optimised for iPadOS, with the ability to drag and drop to import and export images from any location on iPad.

Create your own shortcut keys using a keyboard attachment for an even more streamlined workflow. The final input field in the Offset menu would be the Miter Limit field. The miter limit represents the point in which a miter join transforms into a bevel join.

For example, if you were to set the miter limit to 10 , this means that once a point reaches ten times its original weight, it transforms into a bevel join. In most instances, this is a field you will not have to pay attention to. Knowing how to offset a path in Illustrator will help you to create all kinds of unique designs and illustrations.

Offsets allow you to easily add a border around your object without having to apply a stroke. One of the downsides of using Illustrator for such a task is that the offset tool is obscured within a messy menu system and cannot be accessed with keyboard shortcuts.

As I touched on in my post comparing Affinity Designer vs Illustrator , Affinity Designer has a dedicated tool for creating offsets that can be accessed directly within the toolbar, or by using a keyboard shortcut. It would be great to see Adobe implement something similar for Illustrator. If you have any questions or need clarification on anything from this lesson, simply leave a comment below. Want to learn more about how Adobe Illustrator works?

Check out my Illustrator Explainer Series – a comprehensive collection of over videos where I go over every tool, feature and function and explain what it is, how it works, and why it’s useful. This post may contain affiliate links.