doc082.htm

来自「Reh Hat user manual. really goooood」· HTM 代码 · 共 549 行 · 第 1/2 页

<p><b><tt>RemapCursorPad</tt></b>
This configuration causes the X server to send back different keycodes for 
the keypad arrow keys and cursorpad arrow keys. This is a minor violation of 
the X protocol, but it allows clients to differentiate between these keys.

<p><b><tt>SnfFormat</tt></b> <i><tt>&#60;</tt>number<tt>&#62;</tt> <tt>&#60;</tt>number<tt>&#62;</tt> <tt>&#60;</tt>number<tt>&#62;</tt> <tt>&#60;</tt>number<tt>&#62;</tt></i>
Metro-X X11.5 can read X11.4 SNF (Server Natural Format) fonts. Since there is 
no standard for SNF fonts, the following four numbers can be adjusted to read 
most SNF fonts. The four number parameters represent the following values, 
normally built into the server at compile time:
<blockquote><font size=-1><tt>
<pre>
BITMAP_BIT_ORDER
IMAGE_BYTE_ORDER
GLYPHPADBYTES
BITMAP_SCANLINE_UNIT
</pre>
</tt></font></blockquote>
For example, to read SCO SNF fonts, add this line to the <tt>Xconfig file:</tt>
<blockquote><font size=-1><tt>
<pre>
SnfFormat 1 0 1 1
</pre>
</tt></font></blockquote>
Or, to read SNF fonts compatible with X11 R4 from Interactive Systems 
Corporation, add this line to the Xconfig file:
<blockquote><font size=-1><tt>
<pre>
SnfFormat 1 1 4 4
</pre>
</tt></font></blockquote>

<p><b><tt>Terminate</tt></b>
Terminate causes the server to exit when the last client disconnects. 
Normally xinit kills the X server when the last client disconnects, before 
the server can reset.

<p><b><tt>Trace <tt>&#60;</tt>number<tt>&#62;</tt></tt></b>
This prints additional debugging information.

<p><b><tt>VideoRam <tt>&#60;</tt>number<tt>&#62;</tt></tt></b>
This specifies the amount of video memory on the graphics card, specified in 
terms of 1024-byte units (with one megabyte equal to a value of 1024). The X 
server usually detects how much memory is on the card.

<p><b><tt>VisualClass <tt>&#60;</tt>number<tt>&#62;</tt></tt></b>
This uses the default VisualClass from <tt>/usr/include/X11/X.h</tt>, and is 
based on the following table:

<p><p><a name="f57"></a>
<center>
<table border>
<tr valign=top>
<td colspan=1 align=left nowrap>
VISUAL CLASS </td>
<td colspan=1 align=left nowrap> NUMBER </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap> 
StaticGray </td>
<td colspan=1 align=left nowrap> 0 </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
GrayScale </td>
<td colspan=1 align=left nowrap> 1 </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
StaticColor </td>
<td colspan=1 align=left nowrap> 2 </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
PseudoColor </td>
<td colspan=1 align=left nowrap> 3 </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
TrueColor </td>
<td colspan=1 align=left nowrap> 4 </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
DirectColor </td>
<td colspan=1 align=left nowrap> 5 
</td></tr>
</table>
<p><center>Figure 57:Visual Classes</center>

</center>
<p>

<p>On monochrome monitors the line
<blockquote><font size=-1><tt>
<pre>
VisualClass 1
</pre>
</tt></font></blockquote>
should be added to the Xconfig file.

<p><h3><a name="sB.2.4">B.2.4 Modes</a></h3>
<title>Modes</title>


The last section of the <tt>Xconfig</tt> file is the Mode database (<tt>Modes</tt>). 
It contains the VESA timing specifications for various resolutions. The default 
values work for most graphics cards, but they can be tweaked to center the 
image and adjust its size on the monitor.
Most of the Metro-X servers use this database to configure the card for graphics
mode. The numbers indicate which clock to use from the DisplayConfig file's 
CLOCKS line, and also show the horizontal and vertical timing values. More 
specifically, an example of the numbers are:
<blockquote><font size=-1><tt>
<pre>
``1024x768''  65  1024  1092  1220  1344  768  786  791  810
</pre>
</tt></font></blockquote>

<p>The following table shows the definition of each Modes number from the prior 
example.
<p><a name="f58"></a>
<center>
<table border>
<tr valign=top>
<td colspan=1 align=left nowrap>
VALUE </td>
<td colspan=1 align=left nowrap> Meaning </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap> 
"1024X768" </td>
<td colspan=1 align=left nowrap> Screen Resolution in Pixels </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
65 </td>
<td colspan=1 align=left nowrap> Pixel Clock (MHz) </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
1024 </td>
<td colspan=1 align=left nowrap> Pixels Displayed (H) </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
1092 </td>
<td colspan=1 align=left nowrap> Sync Start (H) </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
1220 </td>
<td colspan=1 align=left nowrap> Sync End (H) </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
1344 </td>
<td colspan=1 align=left nowrap> Total (H) </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
768 </td>
<td colspan=1 align=left nowrap> Pixels Displayed (V) </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
786 </td>
<td colspan=1 align=left nowrap> Sync Start (V) </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
791 </td>
<td colspan=1 align=left nowrap> Sync End (V) </td></tr>
<tr valign=top>
<td colspan=1 align=left nowrap>
810 </td>
<td colspan=1 align=left nowrap> Total (V)
</td></tr>
</table>
<p><center>Figure 58:Modes Definitions</center>

</center>
<p>

<p>These numbers represent the ranges the electron beam traverses per one vertical 
refresh of the screen. They determine where the image is positioned on the 
screen, and what the refresh rate is.
<h4><a name="sB.2.4.1">B.2.4.1 Adjusting the Image Position</a></h4>
<title>Adjusting the Image Position</title>

You can edit the Modes numbers if the screen image does not properly center or 
fill the monitor screen. Be sure to center the image before stretching or 
shrinking it. 
Any adjustments you make will go into effect after restarting the X server.
<b>Centering the Image:</b>
The <tt>Pixels Displayed</tt> numbers must match the desired physical screen 
resolution. The <tt>Sync Start</tt> and <tt>Sync End</tt> numbers must be increased 
or decreased (to move left or right; up or down) at the same time and by the 
same amount, and stay within the range of the <tt>Displayed</tt> and <tt>Total</tt>
 values.
<ul>
<li>Image too far right:
To adjust an image that is too far to the right, increase the <tt>Horizontal 
Sync Start</tt> and <tt>Horizontal Sync End</tt> values equally. 
<li>Image too far left:
To adjust an image that is too far to the left, decrease the <tt>Horizontal 
Sync Start</tt> and <tt>Horizontal Sync End</tt> values equally. 
For example, to adjust an image that is too far to the left, you could begin 
the process by adding 8 to the two horizontal timing numbers (<tt>Sync Start</tt>
and <tt>Sync End</tt>). Make sure that the <tt>Sync End</tt> number does not exceed 
the <tt>Horizontal Total</tt> number.
The same technique applies for vertical positioning:
<li>Image too low:
To adjust an image that is too far to the bottom, decrease the <tt>Vertical 
Sync Start</tt> and <tt>Vertical Sync End</tt> values equally. 
<li>  Image too high:
To adjust an image that is too far to the top, increase the <tt>Vertical Sync 
Start</tt> and <tt>Vertical Sync End</tt> values equally. 
For example, to adjust an image that is too high, you could begin the process 
by adding 8 to the two vertical timing numbers (<tt>Sync Start</tt>  and <tt>Sync 
End</tt>). Make sure that the <tt>Sync End</tt> number does not exceed the 
<tt>Vertical Total</tt> number.
</ul>
<b>Stretching or Shrinking the Image:</b>
The <tt>Pixels Displayed</tt> numbers must match the desired physical screen 
resolution.  The <tt>Total</tt> value is increased or decreased to stretch or 
shrink the image. In addition, to hold the center position, the <tt>Sync Start</tt>
and <tt>Sync End</tt> numbers must be increased or decreased equally, based on 
one-half of the difference in the changed <tt>Total</tt> value. For instance, if 
you added 10 to the <tt>Horizontal Total</tt> value, you would also add 5 to the 
<tt>Horizontal Sync Start</tt> value and 5 to the <tt>Horizontal Sync End</tt> value.
<ul>
<li>Image too narrow horizontally:
To stretch an image that is too narrow horizontally (extra space appears on the 
left and right), increase the <tt>Horizontal Total</tt> by amount x, then add 
one-half of x to both the <tt>Horizontal Sync Start</tt> and <tt>Horizontal Sync 
End</tt> values. 
<li>Image too narrow vertically:
To stretch an image that is too narrow vertically (extra space appears on the 
top and bottom), increase the <tt>Vertical Total</tt> by amount x, then add 
one-half of x to both the <tt>Vertical Sync Start</tt> and <tt>Vertical Sync End</tt>
 values. 
<li>Image too wide horizontally:
To shrink an image that is too wide horizontally (the image extends beyond the 
left and right edges), decrease the <tt>Horizontal Total</tt> by amount x, then 
subtract one-half of x from both the <tt>Horizontal Sync Start</tt> and 
<tt>Horizontal Sync End</tt> values. 
<li>Image too tall vertically:
To shrink an image that is too tall vertically (the image extends beyond the 
top and bottom edges), decrease the <tt>Vertical Total</tt> by amount x, then 
subtract one-half of x from both the <tt>Vertical Sync Start</tt> and <tt>Vertical
Sync End</tt> values. 
</ul>

<p><h4><a name="sB.2.4.2">B.2.4.2 Extensions</a></h4>
<title>Extensions</title>

Extensions are configured in the <tt>/usr/lib/X11/Metro/Extensions</tt> file. 
Most extensions are dynamically loaded; that is, if they are needed they are 
loaded automatically without any additional manual configuration. 
An extension that is ``ON'' is loaded at server startup and never unloaded. An 
extension that is ``DYN'' is dynamically loaded on request by an X client 
<tt>XQueryExtension</tt> call. These extensions display with <tt>XListExtensions</tt>
or <tt>xdpyinfo</tt>. An extension that is ``OFF'' can not be used, nor is it 
displayed with <tt>XListExtensions</tt> or <tt>xdpyinfo</tt>. 

<p><h4><a name="sB.2.4.3">B.2.4.3 Special Notes</a></h4>
<title>Special Notes</title>

<ul>
<li><tt>Multi-Buffering</tt> and <tt>DOUBLE-BUFFER</tt> can not be dynamically 
loaded. They must be set to ``ON'' or ``OFF''.
<li><tt>GLX</tt> (OpenGL) can be dynamically loaded, however <tt>GLX</tt> depends 
on <tt>DOUBLE-BUFFER</tt> being ``ON''. Therefore, to use <tt>GLX</tt>, set 
<tt>DOUBLE-BUFFER</tt> to ``ON'' and <tt>GLX</tt> to ``DYN''.
<li><tt>X3D-PEX</tt> (PEX) can be dynamically loaded, however <tt>X3D-PEX</tt> 
depends on Multi-Buffering being ``ON''. Therefore, to use <tt>X3D-PEX</tt>, set 
<tt>Multi-Buffering</tt> to ``ON'' and <tt>X3D-PEX</tt> to ``DYN''.
</ul>

<p><hr>
<a href="doc083.html"><img src=../icons/next.gif alt="Next"></a>
<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
<a href="doc081.html"><img src=../icons/previous.gif alt="Previous"></a>
<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
<a href="doc123.html"><img src=../icons/index.gif alt="Index"></a>
<hr>
</body></html>