fs why not support create file or dir? about lvgl HOT 9 OPEN

If so, why not use the original file system API directly instead of using the lvgl proxy API?

LVGL can be used in many environments and platform (PC, embedded, many RTOS, many FS libs) and internally LVGL needs to have an abstract way to to open and read images and other assets.

There is no file/directory creation API because the FS API was intended to be used internally by LVGL where just read the assets.

Did you use LVGL's FS in the application code or was it required for the UI itself?

from lvgl.

maybe i want input some text or get some data, i need show it in lvgl, then confirmation, create the file and save it.

Could you tell me a little bit about where lv_fs is mainly used?
I would prefer to use the same file system interface throughout the program, rather than mixing multiple interfaces, which is prone to errors.

from lvgl.

With mode LV_FS_MODE_WR , it will write to file, or create if not exist.

See

from lvgl.

With mode LV_FS_MODE_WR , it will write to file, or create if not exist.

See

lvgl/src/libs/fsdrv/lv_fs_posix.c

Line 111 in 730a3bd

else if(mode == (LV_FS_MODE_WR | LV_FS_MODE_RD)) flags = O_RDWR | O_CREAT;

I know this problem can be solved by modifying the source code of lvgl, but I just raised my doubt. It would be better if the lvgl project could solve this problem in github.

from lvgl.

It's already in LVGL. You can use open a file with the LV_FS_MODE_WR | LV_FS_MODE_RD flags.

from lvgl.

It is a bit field variable, so I think the following solution should be better?

int flags = 0;
if(mode & LV_FS_MODE_RD) flags |= O_RDONLY;
if(mode & LV_FS_MODE_WR) flags |= O_WRONLY | O_CREAT;

from lvgl.

They are defines like this for me:

#define O_RDONLY	     00
#define O_WRONLY	     01
#define O_RDWR		     02

So O_RDONLY | O_WRONLY != O_RDWR

from lvgl.

They are defines like this for me:

#define O_RDONLY	     00
#define O_WRONLY	     01
#define O_RDWR		     02

So O_RDONLY | O_WRONLY != O_RDWR

Well, OK.
But if there are not too many flags, I think we should use bitmaps instead of the original define, which is more efficient.
Such changes are not destructive.
As variables used as flags, there should be no user passing in original values.

from lvgl.

We need some feedback on this issue.

Now we mark this as "stale" because there was no activity here for 14 days.

Remove the "stale" label or comment else this will be closed in 7 days.

from lvgl.