Sponsored Content
Full Discussion: Templates
Contact Us Post Here to Contact Site Administrators and Moderators Templates Post 30153 by him on Thursday 17th of October 2002 12:53:35 PM
Old 10-17-2002
The Original one, you know the one in the vBulletin.com!

Thanks for your reply!
him
 

8 More Discussions You Might Find Interesting

1. Programming

c++ templates problems in g++

what we have: class TClass { public: TClass(); }; template<class T> class FClass<T>: public T { public: FClass(); }; TClass::TClass() { // some code } template<class T> FClass<T>::FClass : T() { // some code } int main (int argc,char* argv) { (3 Replies)
Discussion started by: Marhinado John
3 Replies

2. Programming

site templates?

Are there any web site templates on CGI that allow like this forum software user registration and profiles. I dont need forum software i just need to register and keep profiles of my users on my site. Any suggestions? :confused: Thank you all. (1 Reply)
Discussion started by: solvman
1 Replies

3. HP-UX

Where are SAM user templates stored?

Hey, new here, so be nice! I'm trying to write a little script to automate the user creation process on one of our boxes. But I would like to be able to use the templates that we have set up in SAM. Is the information in these templates stored in a file somewhere, that I can reference in my... (5 Replies)
Discussion started by: paqman
5 Replies

4. Shell Programming and Scripting

Reading from Templates

I am trying to write a script that would retrieve specific information from a template. I have been trying to no avail for the longest. This is what I wrote and it's not working. cat filename | while read F5 F6 do if ] then echo $F5 $F6 fi done Here is the template (filename) CN ... (7 Replies)
Discussion started by: Ernst
7 Replies

5. Solaris

A compilation problem when using templates

Hello life savers, I'm having trouble compiling a specific program. The program was originally written for gcc and was compiled successfully under it. When trying to compile under Solaris 11, I get this error: "Hashtable.h", line 170: Error: Could not find a match for hash needed in... (2 Replies)
Discussion started by: yp515
2 Replies

6. Programming

Templates and header file

I have some C++ code and want to have the class declarations in a .h file and the implementation in the .cpp file. It seems however that for templates everything need to be put in the header (.h) file and will have problems if I try to separate the code to a .cpp file. Is this correct? Is... (1 Reply)
Discussion started by: kristinu
1 Replies

7. Programming

C++ templates

I have the following template codes but some normal functions too and want to group them together. I usually put the implementation of templates in an .ipp file. What would be a good scheme for the normal functions. Put their implementations in a .cpp file, or leave them in the .ipp file? ... (3 Replies)
Discussion started by: kristinu
3 Replies

8. UNIX and Linux Applications

LibreOffice Templates Custom Distro

Hello, I have a custom Linux distro in which I'm trying to get templates for LibreOffice to ship by default. Is there a location they need to be placed or a file that needs to be edited? I've already tried using the template manager and add templates that way. I then copied /usr/templates/ and... (0 Replies)
Discussion started by: TheOuterLinux
0 Replies
xcb_randr_get_screen_resources(3)				   XCB Requests 				 xcb_randr_get_screen_resources(3)

NAME
xcb_randr_get_screen_resources - SYNOPSIS
#include <xcb/randr.h> Request function xcb_randr_get_screen_resources_cookie_t xcb_randr_get_screen_resources(xcb_connection_t *conn, xcb_window_t window); Reply datastructure typedef struct xcb_randr_get_screen_resources_reply_t { uint8_t response_type; uint8_t pad0; uint16_t sequence; uint32_t length; xcb_timestamp_t timestamp; xcb_timestamp_t config_timestamp; uint16_t num_crtcs; uint16_t num_outputs; uint16_t num_modes; uint16_t names_len; uint8_t pad1[8]; } xcb_randr_get_screen_resources_reply_t; Reply function xcb_randr_get_screen_resources_reply_t *xcb_randr_get_screen_resources_reply(xcb_connection_t *conn, xcb_randr_get_screen_resources_cookie_t cookie, xcb_generic_error_t **e); Reply accessors xcb_randr_crtc_t *xcb_randr_get_screen_resources_crtcs(const xcb_randr_get_screen_resources_request_t *reply); int xcb_randr_get_screen_resources_crtcs_length(const xcb_randr_get_screen_resources_reply_t *reply); xcb_generic_iterator_t xcb_randr_get_screen_resources_crtcs_end(const xcb_randr_get_screen_resources_reply_t *reply); xcb_randr_output_t *xcb_randr_get_screen_resources_outputs(const xcb_randr_get_screen_resources_request_t *reply); int xcb_randr_get_screen_resources_outputs_length(const xcb_randr_get_screen_resources_reply_t *reply); xcb_generic_iterator_t xcb_randr_get_screen_resources_outputs_end(const xcb_randr_get_screen_resources_reply_t *reply); xcb_randr_mode_info_t *xcb_randr_get_screen_resources_modes(const xcb_randr_get_screen_resources_request_t *reply); int xcb_randr_get_screen_resources_modes_length(const xcb_randr_get_screen_resources_reply_t *reply); xcb_randr_mode_info_iterator_t xcb_randr_get_screen_resources_modes_iterator(const xcb_randr_get_screen_resources_reply_t *reply); uint8_t *xcb_randr_get_screen_resources_names(const xcb_randr_get_screen_resources_request_t *reply); int xcb_randr_get_screen_resources_names_length(const xcb_randr_get_screen_resources_reply_t *reply); xcb_generic_iterator_t xcb_randr_get_screen_resources_names_end(const xcb_randr_get_screen_resources_reply_t *reply); REQUEST ARGUMENTS
conn The XCB connection to X11. window TODO: NOT YET DOCUMENTED. REPLY FIELDS
response_type The type of this reply, in this case XCB_RANDR_GET_SCREEN_RESOURCES. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. sequence The sequence number of the last request processed by the X11 server. length The length of the reply, in words (a word is 4 bytes). timestamp TODO: NOT YET DOCUMENTED. config_timestamp TODO: NOT YET DOCUMENTED. num_crtcs TODO: NOT YET DOCUMENTED. num_outputs TODO: NOT YET DOCUMENTED. num_modes TODO: NOT YET DOCUMENTED. names_len TODO: NOT YET DOCUMENTED. DESCRIPTION
RETURN VALUE
Returns an xcb_randr_get_screen_resources_cookie_t. Errors have to be handled when calling the reply function xcb_randr_get_screen_re- sources_reply. If you want to handle errors in the event loop instead, use xcb_randr_get_screen_resources_unchecked. See xcb-requests(3) for details. ERRORS
This request does never generate any errors. SEE ALSO
AUTHOR
Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. XCB
2014-06-10 xcb_randr_get_screen_resources(3)
All times are GMT -4. The time now is 05:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy