graphics: Correct various typo error
Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com> Change-Id: I2151bf7d2ce8fc5efddfa269d88c239f87eb23ba
This commit is contained in:
parent
6168f3ebf0
commit
bd4fcebb95
@ -70,11 +70,6 @@ config NX_RAMBACKED
|
||||
It is necessary in that case to provide new graphic content for the
|
||||
extended window area.
|
||||
|
||||
Redraw requests in other cases are also suppressed: Changes to window
|
||||
position, size, etc. As a consequence, some manual updates will be
|
||||
required when certain events occur (like removing a toolbar from a
|
||||
window).
|
||||
|
||||
NOTE: A significant amount of RAM, usually external SDRAM, may be
|
||||
required to use per-window framebuffers.
|
||||
|
||||
@ -107,7 +102,7 @@ config NX_SWCURSOR
|
||||
internal buffer. Neither of those are implemented.
|
||||
|
||||
config NX_HWCURSOR
|
||||
bool "Software cursor support"
|
||||
bool "Hardware cursor support"
|
||||
depends on (FB_HWCURSOR || LCD_HWCURSOR) && EXPERIMENTAL
|
||||
---help---
|
||||
Hardware cursor support has not been implemented, hence the
|
||||
@ -116,7 +111,7 @@ config NX_HWCURSOR
|
||||
endchoice # Cursor support
|
||||
|
||||
config NX_HWCURSORIMAGE
|
||||
bool "Support cursor images"
|
||||
bool "Support hardware cursor images"
|
||||
default n
|
||||
depends on NX_HWCURSOR
|
||||
|
||||
|
@ -55,13 +55,13 @@ Directories
|
||||
|
||||
User callable functions must, instead, be part of a library that can be
|
||||
linked against user applications. This user callable interfaces are
|
||||
provided in sub-directories under nuttx/libnx.
|
||||
provided in sub-directories under nuttx/libs/libnx.
|
||||
|
||||
libnx/nx
|
||||
libs/libnx/nx
|
||||
Client application callable interfaces.
|
||||
|
||||
graphics/nxglib
|
||||
libnx/nxglib
|
||||
libs/libnx/nxglib
|
||||
The NuttX tiny graphics library. The directory contains generic utilities
|
||||
support operations on primitive graphics objects and logic to rasterize directly
|
||||
into a framebuffer. It has no concept of windows (other than the one, framebuffer
|
||||
@ -75,7 +75,7 @@ graphics/nxbe
|
||||
end no longer exists).
|
||||
|
||||
graphics/nxmu
|
||||
libnx/nxmu
|
||||
libs/libnx/nxmu
|
||||
This is the NX multi user "front end". When combined with the generic
|
||||
"back-end" (nxbe), it implements a multi-threaded, multi-user windowing
|
||||
system. The files in this directory present the window APIs described in
|
||||
@ -85,16 +85,16 @@ libnx/nxmu
|
||||
operations from many threads. The multi-user front-end is selected
|
||||
automatically.
|
||||
|
||||
libnx/nxfonts
|
||||
libs/libnx/nxfonts
|
||||
This is where the NXFONTS implementation resides. This is a relatively low-
|
||||
level set of charset set/glyph management APIs. See include/nuttx/nx/nxfonts.h
|
||||
|
||||
libnx/nxtk
|
||||
libs/libnx/nxtk
|
||||
This is where the NXTOOLKIT implementation resides. This toolkit is built on
|
||||
top of NX and works with either the single-user or multi-user NX version. See
|
||||
include/nuttx/nx/nxtk.h
|
||||
|
||||
nuttx/../NxWidgets
|
||||
apps/grahpics/nxwidgets
|
||||
The NxWidgets code is provided as a separate package located outside of the
|
||||
NuttX source tree (probably at this location).
|
||||
|
||||
@ -105,7 +105,7 @@ graphics/vnc
|
||||
Installing New Fonts
|
||||
^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
[Refer to nuttx/libnx/nxfonts/README.txt]
|
||||
[Refer to nuttx/libs/libnx/nxfonts/README.txt]
|
||||
|
||||
Configuration Settings
|
||||
^^^^^^^^^^^^^^^^^^^^^^
|
||||
@ -155,7 +155,7 @@ CONFIG_VNCSERVER and CONFIG_VNCCLIENT
|
||||
Font Selections
|
||||
---------------
|
||||
|
||||
[Refer to nuttx/libnx/nxfonts/README.txt]
|
||||
[Refer to nuttx/libs/libnx/nxfonts/README.txt]
|
||||
|
||||
NxTerm Configuration Settings
|
||||
--------------------------------
|
||||
|
@ -148,8 +148,8 @@ config VNCSERVER_DEBUG
|
||||
default n
|
||||
depends on DEBUG_FEATURES && !DEBUG_GRAPHICS
|
||||
---help---
|
||||
Normally VNC debug output is selected with DEBUG_GRAPHICS. The VNC
|
||||
server server support this special option to enable GRAPHICS debug
|
||||
Normally VNC debug output is selected with DEBUG_GRAPHICS. The
|
||||
VNC server support this special option to enable GRAPHICS debug
|
||||
output for the VNC server while GRAPHICS debug is disabled. This
|
||||
provides an cleaner, less cluttered output when you only wish to
|
||||
debug the VNC server versus enabling DEBUG_GRAPHICS globally.
|
||||
|
Loading…
Reference in New Issue
Block a user