view release on metacpan or search on metacpan
lib/ICC/Shared.pm view on Meta::CPAN
$rhs->[$i - 1][$i] = 3;
$rhs->[$i + 1][$i] = -3;
}
# set endpoint values
$rhs->[0][0] = -3;
$rhs->[1][0] = -3;
$rhs->[$ix][$ix] = 3;
$rhs->[$ix - 1][$ix] = 3;
lib/ICC/Shared.pm view on Meta::CPAN
$rhs->[$i - 1][$i] = 3;
$rhs->[$i + 1][$i] = -3;
}
# set endpoint values
$rhs->[0][0] = -3;
$rhs->[1][0] = -3;
$rhs->[$ix][$ix] = 3;
$rhs->[$ix - 1][$ix] = 3;
view release on metacpan or search on metacpan
lib/IO/Iron/IronMQ/Client.pm view on Meta::CPAN
Get push status for a message. Retrieve the push status for a
particular message which will let you know which subscribers
have received the message, which have failed, how many times
it's tried to be delivered and the status code returned from
the endpoint.
my $info = $iron_mq_queue->get_push_statuses( 'id' => $msg_id );
my @subscribers = (@{info->{'subscribers'}});
Acknowledge / Delete Push Message for a Subscriber.
view release on metacpan or search on metacpan
lib/IO/K8s.pm view on Meta::CPAN
my $k8s = IO::K8s->new(with => ['IO::K8s::Cilium']);
my $cnp = $k8s->new_object('CiliumNetworkPolicy',
metadata => { name => 'allow-dns', namespace => 'kube-system' },
spec => { endpointSelector => { matchLabels => { app => 'dns' } } },
);
print $cnp->to_yaml;
All Cilium kinds are C<Cilium>-prefixed, so there are no collisions with
view release on metacpan or search on metacpan
lib/IO/Multiplex.pm view on Meta::CPAN
$self->{_endloop} = 1;
}
=head2 udp_peer
Get peer endpoint of where the last udp packet originated.
$saddr = $mux->udp_peer($fh);
=cut
view release on metacpan or search on metacpan
lib/IO/Socket/TIPC/Sockaddr.pm view on Meta::CPAN
=head1 DESCRIPTION
TIPC Sockaddrs are used with TIPC sockets, to specify local or remote
endpoints for communication. They are used in the B<bind>(),
B<connect>(), B<sendto>() and B<recvfrom>() calls.
Sockaddrs can be broken down into 3 address-types, I<"name">,
I<"nameseq"> and I<"id">. the I<Programmers_Guide.txt> (linked to in
B<REFERENCES>) explains the details much better than I ever could, I suggest
view release on metacpan or search on metacpan
lib/IPC/Manager/Serializer/JSON/Zstd.pm view on Meta::CPAN
Zstd compression level. Defaults to C<3> (Compress::Zstd's library default).
=item dictionary => $path
Path to a zstd preset dictionary file. Both endpoints must have access to a
dictionary at the same path with the same content. When set, the constructor
loads the file once and reuses it for every C<serialize>/C<deserialize> call.
=back
view release on metacpan or search on metacpan
lib/IPC/MicroSocket.pm view on Meta::CPAN
=head2 Why not ZeroMQ?
I found ZeroMQ to be a lot of effort to use from Perl, and most critically it
does not appear to support both request/response and publish/subscribe message
flows to share the same UNIX socket. To support that in ZeroMQ it would appear
to be necessary to create two separate endpoints, one for each kind of message
flow.
=head2 Why not JSON/YAML/your-favourite-serialisation?
I mostly built this for a few very-small use-cases involving simple byte
view release on metacpan or search on metacpan
lib/IPC/Run.pm view on Meta::CPAN
that both stdout and stderr write to the created pipe.
=item Redirection Filters
Both input redirections and output redirections that use scalars or
subs as endpoints may have an arbitrary number of filter subs placed
between them and the child process. This is useful if you want to
receive output in chunks, or if you want to massage each chunk of
data sent to the child. To use this feature, you must use operator
syntax:
lib/IPC/Run.pm view on Meta::CPAN
=back
=head1 FILTERS
These filters are used to modify input our output between a child
process and a scalar or subroutine endpoint.
=over
=item binary
lib/IPC/Run.pm view on Meta::CPAN
in to one 'meta-harness'.
Allow a harness to be passed in place of an \@cmd. This would allow
multiple harnesses to be aggregated.
Ability to add external file descriptors w/ filter chains and endpoints.
Ability to add timeouts and timing generators (i.e. repeating timeouts).
High resolution timeouts.
view release on metacpan or search on metacpan
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x1,$y1 $x2,$y2";
&$image_clear_func();
$image->line ($x1,$y1, $x2,$y2, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x2,$y2 $x1,$y1, reversal";
&$image_clear_func();
$image->line ($x2,$y2, $x1,$y1, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
view release on metacpan or search on metacpan
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x1,$y1 $x2,$y2";
&$image_clear_func();
$image->line ($x1,$y1, $x2,$y2, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x2,$y2 $x1,$y1, reversal";
&$image_clear_func();
$image->line ($x2,$y2, $x1,$y1, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
view release on metacpan or search on metacpan
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x1,$y1 $x2,$y2";
&$image_clear_func();
$image->line ($x1,$y1, $x2,$y2, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x2,$y2 $x1,$y1, reversal";
&$image_clear_func();
$image->line ($x2,$y2, $x1,$y1, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
view release on metacpan or search on metacpan
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x1,$y1 $x2,$y2";
&$image_clear_func();
$image->line ($x1,$y1, $x2,$y2, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x2,$y2 $x1,$y1, reversal";
&$image_clear_func();
$image->line ($x2,$y2, $x1,$y1, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
view release on metacpan or search on metacpan
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x1,$y1 $x2,$y2";
&$image_clear_func();
$image->line ($x1,$y1, $x2,$y2, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x2,$y2 $x1,$y1, reversal";
&$image_clear_func();
$image->line ($x2,$y2, $x1,$y1, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
view release on metacpan or search on metacpan
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x1,$y1 $x2,$y2";
&$image_clear_func();
$image->line ($x1,$y1, $x2,$y2, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x2,$y2 $x1,$y1, reversal";
&$image_clear_func();
$image->line ($x2,$y2, $x1,$y1, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
view release on metacpan or search on metacpan
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x1,$y1 $x2,$y2";
&$image_clear_func();
$image->line ($x1,$y1, $x2,$y2, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x2,$y2 $x1,$y1, reversal";
&$image_clear_func();
$image->line ($x2,$y2, $x1,$y1, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
view release on metacpan or search on metacpan
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x1,$y1 $x2,$y2";
&$image_clear_func();
$image->line ($x1,$y1, $x2,$y2, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x2,$y2 $x1,$y1, reversal";
&$image_clear_func();
$image->line ($x2,$y2, $x1,$y1, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
view release on metacpan or search on metacpan
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x1,$y1 $x2,$y2";
&$image_clear_func();
$image->line ($x1,$y1, $x2,$y2, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x2,$y2 $x1,$y1, reversal";
&$image_clear_func();
$image->line ($x2,$y2, $x1,$y1, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
view release on metacpan or search on metacpan
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x1,$y1 $x2,$y2";
&$image_clear_func();
$image->line ($x1,$y1, $x2,$y2, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
t/MyTestImageBase.pm view on Meta::CPAN
my $name = "line $x2,$y2 $x1,$y1, reversal";
&$image_clear_func();
$image->line ($x2,$y2, $x1,$y1, $white);
my $bad = (
# endpoints
is_pixel ($image, $x1,$y1, $white, $name)
+ is_pixel ($image, $x2,$y2, $white, $name)
# nothing in surrounding rectangle
+ is_rect ($image, $x1-1,$y1-1, $x2+1,$y2+1, $black, $name));
view release on metacpan or search on metacpan
lib/Image/Base/X11/Protocol/Drawable.pm view on Meta::CPAN
# clipping to signed 16-bit parameters
use constant _LO => -0x8000; # -32768
use constant _HI => 0x7FFF; # +32767
# $x1,$y1, $x2,$y2 are the endpoints of a line.
# Return new endpoints which are clipped to within -0x8000 to +0x7FFF which is
# signed 16-bits for X protocol.
# If given line is entirely outside the signed 16-bit rectangle then return
# an empty list.
#
sub _line_clip {
lib/Image/Base/X11/Protocol/Drawable.pm view on Meta::CPAN
($x2,$y2) = _line_end_clip($x2,$y2, $x1,$y1)
or return;
return ($x1new,$y1new, $x2,$y2);
}
# $x1,$y1, $x2,$y2 are the endpoints of a line.
# Return new values for the $x2,$y2 end which clips it to within
# LO <= x2 <= HI
# LO <= y2 <= HI
#
# If the line is entirely outside LO to HI then return an empty list.
view release on metacpan or search on metacpan
lib/Image/Base.pm view on Meta::CPAN
=head2 Lines
Sloping lines are drawn by a basic Bressenham line drawing algorithm with
integer-only calculations. It ends up drawing the same set of pixels no
matter which way around the two endpoints are passed.
Would there be merit in rounding odd numbers of pixels according to which
way around line ends are given? Eg. a line 0,0 to 4,1 might do 2 pixels on
y=0 and 3 on y=1, but 4,1 to 0,0 the other way around. Or better to have
consistency either way around? For reference, in the X11 drawing model the
lib/Image/Base.pm view on Meta::CPAN
=head2 Image Libraries
The subclasses like GD or PNGwriter which are front-ends to other drawing
libraries don't necessarily use these base algorithms, but can be expected
to something sensible within the given line endpoints or ellipse bounding
box. (Among the image libraries it's surprising how variable the quality of
the ellipse drawing is.)
=head1 SEE ALSO
view release on metacpan or search on metacpan
lib/Image/Bitmap2Paths.pm view on Meta::CPAN
if ($closed < 0) { # loop known to be smooth; stroke_2_strokes() won't find anything except ends
$runs = [[0],[$#$stroke+1]]; # fake corners at ends; [0] means: start at 0, no calculated lines until the next
} else {
($runs, $breaks) = stroke_2_strokes($stroke, \%inCalcEdge, $closed); # Meaning: $runs->[$break] starts a new sub-stroke
}
push @strokes, [$closed, !'blob', $stroke, $runs, $breaks]; # (strokes with endpoints: “openâ€)
}
# warn "found open strokes: ", scalar @strokes, "\n";
my(@closedStrokes, %edgesDone);
my @E;
for my $E (sort keys %$tailEdge) { # Best place to cut a closed stroke — if present.
view release on metacpan or search on metacpan
ccv-src/doc/http.md view on Meta::CPAN
The HTTP API as it is now, only supports 5 major ccv functionalities: BBF, DPM, SWT, TLD and
SIFT. All these APIs are discoverable, you can simply:
curl localhost:3350
and it will return you the list of API endpoints that you can navigate, try one:
curl localhost:3350/dpm/detect.objects
It returns:
ccv-src/doc/http.md view on Meta::CPAN
On Life-cycle of a Request
Whenever you issued a HTTP request, ccv received such request with libev, in asynchronous fashion,
and then dispatch a processing function to another thread with libdispatch, when the data is
ready, ccv will dispatch back to main event loop and send result back. Thus, requests to ccv
won't block each other. Although silly, dummy GET requests to ccv HTTP API endpoints can easily
peak to around 25K requests per second, you shouldn't worry too much about its HTTP performance
(you should more worry about its computer vision algorithms' performance).
On Error Message
ccv's HTTP endpoints doesn't provide informative error messages, if you issued a request that
it cannot handle, will return 400 with 'false' in its body. It may not be a problem for most
of the API endpoints, but it would be for some advanced ones.
On Parameters
All HTTP API's parameters can be easily interpreted through the C API documentation, ccv chooses
reasonable defaults from start, so any of them are optional.
On Security
The HTTP API endpoints are not intended to be exposed to public Internet, you should hide these
behind firewalls.
view release on metacpan or search on metacpan
ds9-interface.html view on Meta::CPAN
include Tcl code specific to DS9's internals, so are not easily
converted into a more generic grammar specification.</p>
<p>Of late encoding of HTTP REST API's has become commonplace via the
OpenAPI Specification (OAS) and RAML initiatives. These encode API
endpoints (<em>paths</em>), parameters and results as <code>YAML</code> or <code>JSON</code> data
structures (<code>RAML</code> only uses <code>YAML</code>). Parameters and results may have
complex structures with types specified by<code>JSON</code> schema.
As most languages in current use have some form of <code>JSON
Schema</code> validation, this provides a simple path to client-side parameter validation.
Tools exist to validate an API description, and to create test servers
view release on metacpan or search on metacpan
lib/Image/ExifTool/TagLookup.pm view on Meta::CPAN
'blocksizemin' => 1,
'blockspercolumn' => 1,
'blocksperframe' => 1,
'blocksperrow' => 1,
'blueadjust' => 1,
'blueendpoint' => 1,
'bluegain' => 1,
'bluegrassscale1' => 1,
'bluegrassscale2' => 1,
'bluegrasstable' => 1,
'bluemask' => 1,
lib/Image/ExifTool/TagLookup.pm view on Meta::CPAN
'encrypt' => 1,
'encryption' => 1,
'enddate' => 1,
'endianness' => 1,
'endmotionvideo' => 1,
'endpoints' => 1,
'endtime' => 1,
'endtimecode' => 1,
'entrypoint' => 1,
'entrytype' => 1,
'environmentmap' => 1,
lib/Image/ExifTool/TagLookup.pm view on Meta::CPAN
'graphicstechnologystandardoutput' => 1,
'gravityvector' => 1,
'grayresponsecurve' => 1,
'graytrc' => 1,
'greenadjust' => 1,
'greenendpoint' => 1,
'greengain' => 1,
'greenmask' => 1,
'greenmatrixcolumn' => 1,
'greenprimary' => 1,
'greensample' => 1,
lib/Image/ExifTool/TagLookup.pm view on Meta::CPAN
'hiddeninfo' => 1,
'hiddenslides' => 1,
'highbitdepth' => 1,
'highisomode' => 1,
'highlightdata' => 1,
'highlightendpoints' => 1,
'highlightmarkers' => 1,
'highnote' => 1,
'highvelocity' => 1,
'hindsightsettings' => 1,
'hintformat' => 1,
lib/Image/ExifTool/TagLookup.pm view on Meta::CPAN
'red1header' => 1,
'red2header' => 1,
'redadjust' => 1,
'redblueflatfield' => 1,
'redcodeversion' => 1,
'redendpoint' => 1,
'redeyedata' => 1,
'redgain' => 1,
'redmask' => 1,
'redmatrixcolumn' => 1,
'redprimary' => 1,
lib/Image/ExifTool/TagLookup.pm view on Meta::CPAN
'seventhlanguage' => 1,
'sfsboundary' => 1,
'sglcoldcacthres1' => 1,
'sglcoldcacthres2' => 1,
'sglcoldcacthres3' => 1,
'shadowendpoints' => 1,
'shadowfilepath' => 1,
'shadowsyncsampletable' => 1,
'shakereductioninfo' => 1,
'shared' => 1,
'shareddata' => 1,
view release on metacpan or search on metacpan
libpng-1.6.17/png.c view on Meta::CPAN
return 0;
}
static int
png_colorspace_endpoints_match(const png_xy *xy1, const png_xy *xy2, int delta)
{
/* Allow an error of +/-0.01 (absolute value) on each chromaticity */
if (PNG_OUT_OF_RANGE(xy1->whitex, xy2->whitex,delta) ||
PNG_OUT_OF_RANGE(xy1->whitey, xy2->whitey,delta) ||
PNG_OUT_OF_RANGE(xy1->redx, xy2->redx, delta) ||
libpng-1.6.17/png.c view on Meta::CPAN
png_colorspace_check_xy(png_XYZ *XYZ, const png_xy *xy)
{
int result;
png_xy xy_test;
/* As a side-effect this routine also returns the XYZ endpoints. */
result = png_XYZ_from_xy(XYZ, xy);
if (result != 0)
return result;
result = png_xy_from_XYZ(&xy_test, XYZ);
if (result != 0)
return result;
if (png_colorspace_endpoints_match(xy, &xy_test,
5/*actually, the math is pretty accurate*/) != 0)
return 0;
/* Too much slip */
return 1;
libpng-1.6.17/png.c view on Meta::CPAN
XYZtemp = *XYZ;
return png_colorspace_check_xy(&XYZtemp, xy);
}
/* Used to check for an endpoint match against sRGB */
static const png_xy sRGB_xy = /* From ITU-R BT.709-3 */
{
/* color x y */
/* red */ 64000, 33000,
/* green */ 30000, 60000,
libpng-1.6.17/png.c view on Meta::CPAN
(colorspace->flags & PNG_COLORSPACE_HAVE_ENDPOINTS) != 0)
{
/* The end points must be reasonably close to any we already have. The
* following allows an error of up to +/-.001
*/
if (png_colorspace_endpoints_match(xy, &colorspace->end_points_xy,
100) == 0)
{
colorspace->flags |= PNG_COLORSPACE_INVALID;
png_benign_error(png_ptr, "inconsistent chromaticities");
return 0; /* failed */
libpng-1.6.17/png.c view on Meta::CPAN
colorspace->flags |= PNG_COLORSPACE_HAVE_ENDPOINTS;
/* The end points are normally quoted to two decimal digits, so allow +/-0.01
* on this test.
*/
if (png_colorspace_endpoints_match(xy, &sRGB_xy, 1000) != 0)
colorspace->flags |= PNG_COLORSPACE_ENDPOINTS_MATCH_sRGB;
else
colorspace->flags &= PNG_COLORSPACE_CANCEL(
PNG_COLORSPACE_ENDPOINTS_MATCH_sRGB);
libpng-1.6.17/png.c view on Meta::CPAN
return 0; /* failed */
}
int /* PRIVATE */
png_colorspace_set_endpoints(png_const_structrp png_ptr,
png_colorspacerp colorspace, const png_XYZ *XYZ_in, int preferred)
{
png_XYZ XYZ = *XYZ_in;
png_xy xy;
libpng-1.6.17/png.c view on Meta::CPAN
/* If the standard sRGB cHRM chunk does not match the one from the PNG file
* warn but overwrite the value with the correct one.
*/
if ((colorspace->flags & PNG_COLORSPACE_HAVE_ENDPOINTS) != 0 &&
!png_colorspace_endpoints_match(&sRGB_xy, &colorspace->end_points_xy,
100))
png_chunk_report(png_ptr, "cHRM chunk does not match sRGB",
PNG_CHUNK_ERROR);
/* This check is just done for the error reporting - the routine always
libpng-1.6.17/png.c view on Meta::CPAN
/* intent: bugs in GCC force 'int' to be used as the parameter type. */
colorspace->rendering_intent = (png_uint_16)intent;
colorspace->flags |= PNG_COLORSPACE_HAVE_INTENT;
/* endpoints */
colorspace->end_points_xy = sRGB_xy;
colorspace->end_points_XYZ = sRGB_XYZ;
colorspace->flags |=
(PNG_COLORSPACE_HAVE_ENDPOINTS|PNG_COLORSPACE_ENDPOINTS_MATCH_sRGB);
view release on metacpan or search on metacpan
examples/scanadf-perl view on Meta::CPAN
#
# S is a scalar value as defined by parse_scalar().
#
# If two consecutive value specs are separated by a comma (,) their
# values are set independently. If they are separated by a dash (-),
# they define the endpoints of a line and all vector values between
# the two endpoints are set according to the value of the
# interpolated line. For example, [0]15-[255]15 defines a vector of
# 256 elements whose value is 15. Similarly, [0]0-[255]255 defines a
# vector of 256 elements whose value starts at 0 and increases to
# 255.
view release on metacpan or search on metacpan
lib/Imager/Plot/Axis.pm view on Meta::CPAN
my %temp = @_;
my $fname = $temp{'GlobalFont'};
my %opts=(
Width => undef, # width includes axis drawing
Height => undef, # height and the endpoints
XRANGE => undef,
YRANGE => undef,
XDRANGE => undef,
YDRANGE => undef,
DATASETS => [],
view release on metacpan or search on metacpan
return $self;
}
# Draws a line from one point to the other
# the endpoint is set if the endp parameter is set which it is by default.
# to turn of the endpoint being set use endp=>0 when calling line.
sub line {
my $self=shift;
my $dflcl=i_color_new(0,0,0,0);
my %opts=(color=>$dflcl,