Comic touches keeps Rain-Slick Precipice fun


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Comic touches keeps Rain-Slick Precipice fun
# 1  
Old 06-09-2008
Comic touches keeps Rain-Slick Precipice fun

Mon, 09 Jun 2008 18:00:00 GMT
When edgy, risque, and retro all come together in a video game, smart people stay off the street. Off the streets of New Arcadia, circa 1922, that is, because that's where evil seems to thrive in Episode 1 of On the Rain-Slick Precipice of Darkness, a newly released game from Hothead Games and Penny Arcade. We first wrote about it last fall, and the game has just been released for Linux, Mac, Windows, and Xbox platforms. Now that we finally have Episode 1 in hand, here's our review.


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Solaris

Any slick way to go from Z to gz??

Morning Everyone, I'm still rather new to Unix and please forgive me if this is a simple question. I have a bunch of old zipped files, ending in Z. Is there a way to gzip them -9, without having to uncompress/recomress? I am trying to get them max compressed. Thank you!! (5 Replies)
Discussion started by: smckech1972
5 Replies
Login or Register to Ask a Question
funimagerowput(3)						SAORD Documentation						 funimagerowput(3)

NAME
FunImageRowPut - put row(s) of an image SYNOPSIS
#include <funtools.h> void *FunImageRowPut(Fun fun, void *buf, int rstart, int rstop, int dim1, int dim2, int bitpix, char *plist) DESCRIPTION
The FunImageRowPut() routine writes one or more image rows to the specified FITS image file. The first argument is the Funtools handle returned by FunOpen(). The second buf argument is a pointer to the row data buffer, while the third and fourth arguments specify the starting and ending rows to write. Valid rows values range from 1 to dim2, i.e., row is one-valued. The dim1and dim2 arguments that follow specify the dimensions, where dim1 corresponds to naxis1 and dim2 corresponds to naxis2. The bitpix argument data type of the image and can have the following FITS-standard values: o 8 unsigned char o 16 short o 32 int o -32 float o -64 double For example: double *drow; Fun fun, fun2; ... open files ... /* get section dimensions */ FunInfoGet(fun, FUN_SECT_DIM1, &dim1, FUN_SECT_DIM2, &dim2, 0); /* allocate one line's worth */ drow = malloc(dim1*sizeof(double)); /* retrieve and process each input row (starting at 1) */ for(i=1; i <= dim2; i++){ if( !FunImageRowGet(fun, drow, i, i, "bitpix=-64") ) gerror(stderr, "can't FunImageRowGet: %d %s ", i, iname); ... process drow ... if( !FunImageRowPut(fun2, drow, i, i, 64, NULL) ) gerror(stderr, "can't FunImageRowPut: %d %s ", i, oname); } ... The data are assumed to be in the native machine format and will automatically be swapped to big-endian FITS format if necessary. This behavior can be over-ridden with the convert=[true|false] keyword in the plist param list string. When you are finished writing the image, you should call FunFlush() to write out the FITS image padding. However, this is not necessary if you subsequently call FunClose() without doing any other I/O to the FITS file. SEE ALSO
See funtools(7) for a list of Funtools help pages version 1.4.2 January 2, 2008 funimagerowput(3)