Lines Matching refs:file
8 any type of file system. A file system is identified by an assigned
10 ``'S'``, a file can be reached using ``"S:/path/to/file.txt"``. See details
34 As mentioned above, a file system is identified by an assigned identifier letter.
36 the appropriate registered file-system driver for a given path.
40 You register a driver for your file system and assign it an identifier letter. This
41 letter must be unique among all registered file-system drivers, and in the range [A-Z]
44 Later, when using paths to files on your file system, you prefix the path with that
59 | +-- This part gets passed to the OS-level file-system functions.
62 driver (i.e. set of functions) that apply to that file system.
68 **Examples for Unix-like file systems:**
75 **Examples for Windows/DOS-like file systems:**
84 "Z:" is used to look up the driver for that file system in the list of all file-system
111 drv.open_cb = my_open_cb; /* Callback to open a file */
112 drv.close_cb = my_close_cb; /* Callback to close a file */
113 drv.read_cb = my_read_cb; /* Callback to read a file */
114 drv.write_cb = my_write_cb; /* Callback to write a file */
115 drv.seek_cb = my_seek_cb; /* Callback to seek in a file (Move cursor) */
141 ``path`` is the path after the drive letter (e.g. "S:path/to/file.txt" -> "path/to/file.txt").
144 The return value is a pointer to a *file object* that describes the
145 opened file or ``NULL`` if there were any issues (e.g. the file wasn't
146 found). The returned file object will be passed to other file system
165 This file also provides a template for new file-system drivers you can use if the
171 As of this writing, the list of already-available file-system drivers can be enabled
191 If you are using one of the following file-system drivers:
209 **Examples for Unix-like file systems:**
215 **Examples for Windows/DOS-like file systems:**
231 The example below shows how to read from a file:
237 res = lv_fs_open(&f, "S:folder/file.txt", LV_FS_MODE_RD);
304 config option is set to a value greater than zero. Each open file will
307 Generally speaking, file buffering can be optimized for different kinds
312 \>= the size of the file, ``read`` will only be called once. This strategy is good
313 for linear reading of large files but less helpful for short random reads across a file bigger than…
316 is if the file contents are expected to change by an external factor like with special OS files.
332 at the file position?"}}
342 --> G["seek the real file to the end
347 from the real file to the
349 H -->|no| J["eagerly read the real file
355 B -->|no| K["seek the real file to
356 the file position"]
360 L -->|yes| M["read the real file to
362 L -->|no| N["eagerly read the real file
380 to determine where the end of the file is.