TRAPS:  This is another question that pits two values, in this case loyalty and honesty,  against one another.

BEST ANSWER:  Remember the  rule stated earlier:  In any conflict between values,  always choose integrity.

Example:  I  believe that when evaluating anything, it's important to emphasize the positive. What do I like about this idea?"

"Then, if you have reservations, I certainly want to point them out, as specifically, objectively and factually as I can. "

"After all, the most important thing I owe my boss is honesty.  If he can't count on me for that, then everything else I may do or say could be questionable in his eyes." Not sure about that one.

"Of course, if he overrules me and says, 'no, let's do it my way,' then I owe  him my full and enthusiastic support to make it work as best it can."

 

A standard that lets you specify a unique label for the set of element names defined by a DTD. A document using that DTD can be included in any other document without having a conflict between element names. The elements defined in your DTD are then uniquely identified so that, for example, the parser can tell when an element should be interpreted according to your DTD rather than using the definition for an element in a different DTD.

GDI is an acronym for Graphics Device Interface. The GDI allows you to draw on your windows. It is a device independent output model in the sense that the graphics code that you write for drawing will work on any video output which has a Windows driver.  In order to avoid one window interfering with another while drawing output on the screen GDI uses a mechanism called as device context to avoid this conflict. So when a window draws on a screen, printer or any other output device, it doesn't output pixels directly on the device. Instead it draws to a logical surface represented by a "device context" (DC). A DC is a data structure that has all information that GDI needs to know.  Before a Windows program draws anything on the screen it acquires a DC handle from the GDI and then passes this handle back to the GDI each time it calls the GDI output function. In MFC a DC encapsulates the GDI functions that a program uses to generate output. MFC's CDC class wraps a Windows device context and the GDI functions into one package. CPaintDC and CClientDC are subclasses of CDC and represent the different types of device contexts that windows applications use. E.g. CDC* pDC = GetDC(); //do some drawing Release (pDC);

The Device Manger will display an exclamation point (!) inside a yellow circle whenever a device is experiencing a direct hardware conflict with another device. The nature of the problem is described in the device's Properties dialog box.

When a device conflict is suspected, simply click the offending device in the listing, rightclick on the item and select Properties from the pop-up menu, and then click the Resources tab to examine the Conflicting Device's List. You can also access the Properties window by doubleclicking on the device driver name.

To install a non-PnP device on a specific COM port (that is, COM2), you must first disable that port in the system's CMOS settings in order to avoid a device conflict. If not, the system might try to allocate that resource to some other device, since it has no way of knowing that the non-PnP device requires it.