Sponsored Content
Full Discussion: Proper Forum Etiquette
Contact Us Post Here to Contact Site Administrators and Moderators Proper Forum Etiquette Post 27735 by auswipe on Thursday 5th of September 2002 05:10:05 PM
Old 09-05-2002
Quote:
Originally posted by RTM
You aren't going to change a thing. You could probably start up a new name/login on here and only post to questions that fail to give detail with "What OS and version?" and become a Sustaining member in five months.
And I've been doling out good information just to get to Sustaining Member level!?! Smilie

I understand that the one line type questions can get annoying but I would rather put up a good front instead of a true cynical self that looks at the messages and yells "L-user!" It is my hopes that I am able to help and that person becomes a productive member of the forum.

You know what burns my hide? I like to at least get a "Hey, it worked" response after a solution has been posted. Sometimes a response is never given and future thread readers won't know if the solution worked or not.

You know what really burns my hide but is totally idiotic? I really like to know where people are located that post messages. Sometimes I read a message and think, "I betcha that person is located in XXXX part of the world" only to have the Location field left out. Totally insignificant but it bugs me sometimes.

Okay, but to the normal wanna-be helpful Auswipe. Smilie
 

6 More Discussions You Might Find Interesting

1. IP Networking

Proper routing

I have a series of new machines that are internet facing (have IP's that are accessible via the 'net) and it has internal facing interfaces. I need to be able to communicate back to the internal network to a specific server which processes monitoring and e-mail traffic. I've been told that I should... (3 Replies)
Discussion started by: BOFH
3 Replies

2. UNIX for Dummies Questions & Answers

Proper use of prune...

My goal was to find any directories inside of any directory called "09_Client Original" not modified in the last 30 days. $ find /Volumes/Jobs_Volume/ -type d -name "09_Client Original" -exec find {} -mtime +30 -type d -maxdepth 1 \; The results of this find are passed along in a perl script... (1 Reply)
Discussion started by: guriboy
1 Replies

3. Post Here to Contact Site Administrators and Moderators

Forum etiquette and contact information

I got the following message I tried to send the following reply:Please excuse me for not being more familiar with this forums conventions. I was not aware that I included a personal message. Please help me by: 1. So that I can avoid this problem in the future, please let me know what part of my... (2 Replies)
Discussion started by: lmjennings44094
2 Replies

4. UNIX for Dummies Questions & Answers

Proper syntax

I'm new to Unix, and just had a quick question. I'm writing a bash script, and I was wondering what proper programming etiquette was for piping. How many pipes is too many pipes? OLDEST=$(find . -maxdepth 1 -type d -newermt 2012-07-01 ! -newermt 2012-07-30 | xargs ls -1td | tail -2) echo... (1 Reply)
Discussion started by: jrymer
1 Replies

5. What is on Your Mind?

Forum Update: Disabled Home Page Forum Statistics for Guests (Not Registered)

Just a quick update; to speed up the forums, I have disabled the forum statistics on the home page for non registered users. No changes for registered users. (0 Replies)
Discussion started by: Neo
0 Replies

6. What is on Your Mind?

Mobile: Advanced Forum Statistics to Forum Home Page

For mobile users, I have just added a "first beta" Advanced Forum Statistics to the home page on mobile using CSS overflow:auto; so you can swipe if you need to see more. Google Search Console mobile usability says this page is "mobile friendly" so perhaps this will be useful for some of our... (12 Replies)
Discussion started by: Neo
12 Replies
SoReadError(3)							       Coin							    SoReadError(3)

NAME
SoReadError - The SoReadError class is used during model import operations. During model file import, this class will be used to output any error or warning messages. SYNOPSIS
#include <Inventor/errors/SoReadError.h> Inherits SoError. Public Member Functions virtual SoType getTypeId (void) const Static Public Member Functions static void setHandlerCallback (SoErrorCB *const function, void *const data) static SoErrorCB * getHandlerCallback (void) static void * getHandlerData (void) static SoType getClassTypeId (void) static void post (const SoInput *const input, const char *const format,...) static void initClass (void) Protected Member Functions virtual SoErrorCBPtr getHandler (void *&data) const Additional Inherited Members Detailed Description The SoReadError class is used during model import operations. During model file import, this class will be used to output any error or warning messages. Depending on your application, setting up your own error handler callbacks for SoReadError might be a good idea. Member Function Documentation void SoReadError::setHandlerCallback (SoErrorCB *constfunction, void *constdata) [static] This method sets the error handler callback for messages posted via this class. Note that this will not override the error/debug message handler for subclasses, these will have to be overrided by calling the subclass' setHandlerCallback() method. See also: defaultHandlerCB() Reimplemented from SoError. SoErrorCB * SoReadError::getHandlerCallback (void) [static] Returns the error handler callback for messages posted via this class. Reimplemented from SoError. void * SoReadError::getHandlerData (void) [static] This method returns the pointer used for passing data back to the callback handler method. Reimplemented from SoError. SoType SoReadError::getClassTypeId (void) [static] This static method returns the SoType for this class. See also: getTypeId() Reimplemented from SoError. SoType SoReadError::getTypeId (void) const [virtual] This method returns the SoType of a particular object instance. See also: getClassTypeId() Reimplemented from SoError. void SoReadError::post (const SoInput *constin, const char *constformat, ...) [static] Method used from import code to post error or warning messages for model files which are not 100% compliant to the format specification. The messages will be wrapped within information on line number, file offset etc. void SoReadError::initClass (void) [static] This method takes care of initializing all static data for the class. Reimplemented from SoError. SoErrorCB * SoReadError::getHandler (void *&data) const [protected], [virtual] This is just a convenience wrapper around the getHandlerCallback() and getHandlerData() methods. Reimplemented from SoError. Author Generated automatically by Doxygen for Coin from the source code. Version 3.1.3 Wed May 23 2012 SoReadError(3)
All times are GMT -4. The time now is 10:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy