view release on metacpan or  search on metacpan

devel/composite.pl  view on Meta::CPAN

    my $pixmap = $X->new_rsrc;
    $X->CompositeNameWindowPixmap ($window, $pixmap);
    $X->QueryPointer($X->{'root'}); # sync
  }
  {
    my $pixmap = $X2->new_rsrc;
    $X2->CompositeNameWindowPixmap ($window, $pixmap);
    $X2->QueryPointer($X->{'root'}); # sync
  }

  my $overlay_window = $X->CompositeGetOverlayWindow ($window);
  $X->QueryPointer($X->{'root'}); # sync
  ### overlay_window: sprintf '%X', $overlay_window

  {
    my $overlay_window = $X2->CompositeGetOverlayWindow ($window);
    $X2->QueryPointer($X2->{'root'}); # sync
    ### overlay_window: sprintf '%X', $overlay_window
  }

  $X->CompositeReleaseOverlayWindow ($overlay_window);
  $X->QueryPointer($X->{'root'}); # sync


  exit 0;
}

lib/X11/Protocol/Ext/Composite.pm  view on Meta::CPAN

association with C<$window> is lost.  If C<$window> is mapped and redirected
again later then it has a new off-screen storage and a new
C<CompositeNameWindowPixmap()> must be called to get a new pixmap for it.

=back

=head2 Composite 0.3

=over

=item C<$overlay_window = $X-E<gt>CompositeGetOverlayWindow ($window)>

Return the composite overlay window for the screen of C<$window>.

This window covers the whole screen and is always above ordinary windows but
below any screen saver, and doesn't appear in a C<QueryTree()>.  It's
created when the first client asks for it, and shared by any further clients
who ask.

=item C<$X-E<gt>CompositeReleaseOverlayWindow ($window)>

Release the composite overlay window for the screen of C<$window>.  When all
clients release it the overlay window is destroyed.

=back

=head1 SEE ALSO

L<X11::Protocol>,
L<X11::Protocol::Ext::XFIXES>,
L<X11::Protocol::Ext::DOUBLE_BUFFER>

"Composite Extension", Version 0.4, 2007-7-3,

lib/X11/Protocol/Ext/TOG_CUP.pm  view on Meta::CPAN

    [ $pixel, $red16, $blue16, $green16, $alloc_flags ]

C<$red16>, C<$blue16> and C<$green16> are RGB colour components in the range
0 to 65535.  C<$alloc_flags> is currently unused.

Reserved colours are pre-allocated and unchanging.  The core protocol
specifies C<$X-E<gt>{'black_pixel'}> and C<$X-E<gt>{'white_pixel'}> and
they're included in the result, plus any further colours which might be
reserved.

For example under the MS-DOS graphical overlay manager there's a certain set
of "desktop" colours which a server on that system might treat as reserved.

=item C<@colors = $X-E<gt>CupStoreColors ($colormap, [$pixel,$red16,$green16,$blue16],...)>

Allocate read-only colours in C<$colormap> at particular pixels.

Each argument is an arrayref of desired pixel and RGB colour.
(A C<$do_mask> parameter can be present at the end too but is unused and can
be omitted.)