Graphics state on iOS

To traverse the list of changes in the graphics state.

PTGSChangesIterator *gs_itr = [reader GetChangesIterator];
for (; [gs_itr HasNext]; [gs_itr Next]) 
{
  switch([gs_itr Current])
  {
    case e_pttransform :
      // 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 e_ptline_width :
      // gs.GetLineWidth();
      break;
    case e_ptline_cap :
      // gs.GetLineCap();
      break;
    case e_ptline_join :
      // gs.GetLineJoin();
      break;
    case e_ptmiter_limit :
      // gs.GetMiterLimit();
      break;
    case e_ptdash_pattern :
      {
        // std::vector<double> dashes;
        // gs.GetDashes(dashes);
        // gs.GetPhase()
      }
      break;
    default:
      break;
  }
}

PDF Data Extraction (Images, Text, Paths)
Full code sample which illustrates how to extract data, do color conversion, image normalization, and how to process changes in the 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.

if ([reader IsChanged:e_ptline_width])
{
   // line width was changed.
}