A Sad Day for Smarty Jones! Post: 51927

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script to find previous month last day minus one day timestamp

Hi All, I need to find the previous month last day minus one day, using shell script. Can you guys help me to do this. My Requirment is as below: Input for me will be 2000909(YYYYMM) I need the previous months last day minus 1 day timestamp. That is i need 2000908 months last day minus ...

2. What is on Your Mind?

Does modernity make you sad?

One more "on my mind" question ('cause it's constantly on my mind): does modern technology style make you sad and wishing PCs were like they used to be in 90's? I mean we had awesome UIs like motif, win3.1, warp3/4, cde, etc... HDDs used to load with sound. Web used to be a text on a white...

3. AIX

Sad me - or Happy me? Undecided re: AIX 7.2

AIX 7.2 - needs POWER7 or later With AIX 6.1 it was POWER4 or later - then I was "Happy Me!" because I already had a POWER4 system. With AIX 7.2 - for now I am "sad me" because I do not have a POWER7. However, next week I am going to be speaking at the POWER TechU in Cannes (look me up if you...

LEARN ABOUT X11R4

dmxchangescreensattributes

DMXChangeScreensAttributes(3X)											    DMXChangeScreensAttributes(3X)

NAME

       DMXChangeScreensAttributes - change back-end screen attributes

SYNOPSIS

       #include <X11/extensions/dmxext.h>

       int DMXChangeScreensAttributes(Display *dpy,
				      int screen_count,
				      int *screens,
				      int mask_count,
				      unsigned int *masks,
				      DMXScreenAttributes *attr,
				      int *error_screen);

DESCRIPTION

       DMXChangeScreensAttributes()  changes  the  geometries  and  positions  of  the	DMX screen and DMX root windows on the back-end X servers.
       screen_count specifies the number of screens to be changed.  For each screen, the screen number is placed in screens, an attribute mask	is
       placed in masks, and a DMXScreenAttributes structure is included in attr.

       An explanation of the DMXScreenAttributes structure is given in DMXGetScreenAttributes(3X).

       The values that are used to compute each value in masks are as follows

       DMXScreenWindowWidth
       DMXScreenWindowHeight
       DMXScreenWindowXoffset
       DMXScreenWindowYoffset
       DMXRootWindowWidth
       DMXRootWindowHeight
       DMXRootWindowXoffset
       DMXRootWindowYoffset
       DMXRootWindowXorigin
       DMXRootWindowYorigin

       In  general, mask_count should be equal to screen_count.  However, as a convenience, mask_count may be less than screen_count, and the last
       entry in masks will then be used for all of the remaining screens.  For example, this allows  identical	changes  to  be  made  to  several
       screens using only one mask.

RETURN VALUE

       On  success,  0	is returned.  Otherwise, error_screen is set to the value of the first screen in the list that caused the error and a non-
       zero value is returned.	If screen_count or mask_count is less than 1, or if any of the attribute values are  not  within  the  appropriate
       bounding boxes, DmxBadValue is returned.  If a protocol error occurs, DmxBadReply is returned.

       DMXChangeScreensAttributes()  can  generate BadLength (if the data provided does not match the data implicitly required by the screen_count
       and mask_count values), BadValue (if the values in screens are not valid), and BadAlloc errors.

SEE ALSO

       DMXGetScreenCount(3X), DMXGetScreenAttributes(3X), DMX(3X), Xdmx(1)

X Version 11							   libdmx 1.0.2 				    DMXChangeScreensAttributes(3X)