> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/xamarin/edit-page-content/graphics-state.md).

# Graphics state in Xamarin

Learn how to extract data, do color conversion, and process changes in the graphics state with Apryse SDK. Explore full code samples for PDF data extraction. The Apryse Xamarin SDK streamlines secure,

To traverse the list of changes in the graphics state.

{% tabs %}
{% tab title="C#" %}
{% code lineNumbers="true" %}

```csharp
GSChangesIterator gs_itr = reader.GetChangesIterator();
for ( ; gs_itr.HasNext(); gs_itr.Next())
{
  switch(gs_itr.Current())
  {
    case GState.GStateAttribute.e_transform :
      // Get transform matrix for this element. Unlike path.GetCTM() 
      // that return full transformation matrix gs.GetTransform() return 
      // only the transformation matrix that was installed for this element.
      //
      // gs.GetTransform();
      break;
    case GState.GStateAttribute.e_line_width :
      // gs.GetLineWidth();
      break;
    case GState.GStateAttribute.e_line_cap :
      // gs.GetLineCap();
      break;
    case GState.GStateAttribute.e_line_join :
      // gs.GetLineJoin();
      break;
    case GState.GStateAttribute.e_miter_limit :
      // gs.GetMiterLimit();
      break;
    case GState.GStateAttribute.e_dash_pattern :
    {
      // double[] dashes;
      // gs.GetDashes(dashes);
      // gs.GetPhase()
      break;
    }
    // Etc.
  }
}
```

{% endcode %}
{% endtab %}
{% endtabs %}

[PDF Data Extraction (Images, Text, Paths)](/xamarin/get-started/samples.md#elementreaderadv) Full code sample which illustrates how to extract data, do color conversion, image normalization, and how to process changes in the graphics state.

## About graphics state

After reading an Element using `ElementReader.Next()`, it is possible to access all graphical attributes of the Element through its graphics state. Some applications are more interested in *changes* in the graphics state than attribute values. For example, a transition from one Element to another may not involve changes in the graphics state. Or, perhaps, there may be changes only to a couple of attributes. In these cases, it isn't efficient to make memberwise comparisons between the old and current graphics states.

To make this easier and more efficient, Apryse SDK offers an API to enumerate the list of changes between subsequent Elements.

It's also possible to query ElementReader for changes to a specific attribute:

{% tabs %}
{% tab title="C#" %}
{% code lineNumbers="true" %}

```csharp
if (reader.IsChanged(GState.GStateAttribute.e_line_width))
{
   // line width was changed.
}
```

{% endcode %}
{% endtab %}
{% endtabs %}

Note that the list of modified attributes is accumulated when calling `ElementReader.Next()`. To clear the list of modified attributes use `ElementReader.ClearChangeList()` method. A call to `ClearChangeList()` serves as a marker in the display list from which further changes in the graphics state are tracked.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/xamarin/edit-page-content/graphics-state.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.