We do need an up-to-date PDF doc for v7, but why was it pulled down? maybe it's too hard to keep up with new commits?

Hi,

I dont know if here are the right place to inform this, but.....

Link: https://docs.littlevgl.com/en/html/get-started/quick-overview.html
Quick overview:
Implement and register a function which can read an input device. E.g. for a touch pad:
I think are missing this variable(struct) declaration in first line.
lv_indev_drv_t indev_drv;

Thank's.

Describe the bug

The example section in the online documentation (containing the example image and code fragments) is not currently being displayed for some widget types.

To Reproduce

These don't work:

https://docs.littlevgl.com/en/html/object-types/ddlist.html
https://docs.littlevgl.com/en/html/object-types/list.html
https://docs.littlevgl.com/en/html/object-types/page.html

These do:

https://docs.littlevgl.com/en/html/object-types/win.html
https://docs.littlevgl.com/en/html/object-types/table.html

Expected behavior

The example sections were working until very recently.

Screenshots

Additional context

I tried this in Chrome 81 and Firefox 76 and also tried emptying the browser cache and doing a hard refresh.

I have been working for the past few hours on the necessary Actions infrastructure for the documentation to rebuild itself whenever a commit is pushed to the dev, latest, or release/v7 branches.

That logic is functioning for the most part now, so I am trying to switch docs.lvgl.io to serve pages from the gh-pages branch. Unfortunately, GitHub Pages is doing some strange caching and refuses to properly pick up on the CSS from gh-pages (it works fine from master).

Any ideas why this might be happening? I believe everything has been set up on the automation end correctly; this seems to be a Pages issue.

In this section the link to the live demo is broken.

Hi,

Is there a tool to find broken (404) links on the documentation automatically?

I have a question about the using of label widget in Arduino. I created a label that uses the following code in "setup" function:
lv_obj_t * label1 = lv_label_create(scr1, NULL); // yeah I created a screen and acted it.
lv_label_set_long_mode(label1, LV_LABEL_LONG_BREAK); /Break the long lines/
lv_label_set_align(label1, LV_LABEL_ALIGN_RIGHT); /Center aligned lines/
lv_label_set_text(label1, temperchar);
lv_obj_add_style(label1, LV_LABEL_PART_MAIN, &label_style);
lv_obj_set_width(label1, 150);
lv_obj_align(label1, NULL, LV_ALIGN_CENTER, -10, 80);

And then, I want to change the text using "lv_label_set_text(label1, temperchar);" in the "Loop" function, but the debug program says that I didn't define the "label1".

I tried to create the label behind the "setup" function using "lv_obj_t * label1 = lv_label_create(scr1, NULL); ". However, when I upload my program to the ESP32 board, it has frozen, and the serial said the following:

rst:0x10 (RTCWDT_RTC_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5856
entry 0x400806a8

I don't know how to solve this problem. I hope you can help me with this problem.

Hi,

I'm using a container inside another container and would like to remove the border of it or make it the same color as the background (highlighted in yellow):

So I looked up in the docs and could't find the refered lv_cont_set_style function. I checked the lv_examples demo widgets example and the container style are being edited like so (with lv_obj_add_style):

    lv_obj_t * h = lv_cont_create(parent, NULL);
    lv_cont_set_layout(h, LV_LAYOUT_PRETTY_MID);
    lv_obj_add_style(h, LV_CONT_PART_MAIN, &style_box);
    lv_obj_set_drag_parent(h, true);

    lv_obj_set_style_local_value_str(h, LV_CONT_PART_MAIN, LV_STATE_DEFAULT, "Basics");

So my question:
Is the lv_cont_set_style function deprecated and should we use lv_obj_add_style instead?

EDIT
Got it working with lv_obj_set_style_local_border_opa(pulses_buttons_cont, LV_CONT_PART_MAIN, LV_STATE_DEFAULT, LV_OPA_0);, I don't know if only the container docs should be updated or all of the widgets.

When clicking on the Generic Events (and Special Events) hyperlink of the Spinbox documentation

I get a 404 page

The link is https://docs.lvgl.io/overview/event.html#generic-events, the correct link seems to be https://docs.lvgl.io/latest/en/html/overview/event.html#generic-events and https://docs.lvgl.io/overview/event.html#special-events should be replaced with https://docs.lvgl.io/latest/en/html/overview/event.html#special-events.

Hi,

I'm not very familiar with the docs page (https://docs.littlevgl.com/), is it up to date? Some of the pages i been translating still on English.

Regards

Hi,

v6.0 and the new docs have been released. Translating the docs has now started.

If you are interested in the translation please volunteer here to discuss the details.

When you read the English documentation you will surely find typos, grammatical errors, or maybe sentences which don't make sense at all. In this case please send PRs.

If a part was difficult to understand please also notify about it.

How to integrate VNC server to Littlevgl, then user can visit the UI from browser or other VNC client.
Thanks.

Currently, we have a conf.py file for each language. There doesn't seem to be anything language-specific within each file, so can we symlink them and only have one actual conf.py being used?

I came across this while looking for the spot to update the documentation's version number (as it still says 6.0 rather than 6.1).

Can API PDF doc upload to github? Thank you!

i i had created below button how to change its font size?

// create button lv_obj_t * btnSystemOnOFF = lv_btn_create(window, NULL); lv_obj_align(btnSystemOnOFF, NULL, LV_ALIGN_IN_TOP_RIGHT, -24, 40); lv_obj_set_size(btnSystemOnOFF, 125, 40); lv_btn_set_toggle(btnSystemOnOFF, true); lv_btn_toggle(btnSystemOnOFF); // button label ButtonLabel = lv_label_create(btnSystemOnOFF, NULL); lv_label_set_text(ButtonLabel, "System ON"); // button action lv_imgbtn_set_action(btnSystemOnOFF, LV_BTN_ACTION_CLICK, btn_click_SystemOnOFF);

hi,
how to use font converter to get arial 15 font size?

Chinese PDF encoding error, Chinese characters are garbled

I am concerned that people will submit pull requests without regenerating the documentation. How do you plan to handle that?

I was thinking that having some method of auto-generating documentation after a push would be nice, but I'm not sure if that can be done without a server running 24/7. 😕

The current DuckDuckGo/Bing/Google index state is rather sad, it would be reasonable to autogenerate a sitemap and publish that to make the documentation more accessible.

• STM (ChromeART, LTDC, projects, best practices)
• ESP (project, best practice)
• mbed?
• C++

Copies is spelt "Copyes" in the image in the banner:

https://github.com/lvgl/docs/blob/latest/_static/img/home_banner.jpg

There's no LV_LABEL_LONG_DOTS but LV_LABEL_LONG_DOT, please fix them in lv_label doc for multiple languages

There are two misspellings in the documentation

✅ Generation

• 2018-11-26 07:38

The docs says:
The Chart’s main part is called LV_CHART_PART_BG and it uses all the typical background properties. The text style properties determine the style of the axis texts and the line properties determine ticks’ style. Padding values add some space on the sides thus it makes series area smaller. Padding also can be used to make space for axis texts and ticks.
The background of the series is called LV_CHART_PART_SERIES_BG and it’s placed on the main background. The division lines, and series data is drawn on this part. Besides the typical background style properties the line style properties are used by the division lines. The padding values tells the space between the this part and the axis texts.

Long question: for the 3rd element (LV_CHART_PART_SERIES) it's easy to see what styles can be changed as they are clearly listed. But for above first 2 (LV_CHART_PART_BG and LV_CHART_PART_SERIES_BG) it's not. It is said that they use typical background properties.

In the Style chapter, 4.4.9 Properties these categories are listed:

• Mixed properties
• Padding and margin properties
• Background properties
• Border properties
• Outline properties
• Shadow properties
• Pattern properties
• Value properties
• Text properties
• Line properties
• Image properties
• Transition properties
• Scale properties
  And in the end says:
  The ”typical background” properties are:
  • Background
  • Border
  • Outline
  • Shadow
  • Pattern
  • Value

Which implies that these are not among ”typical background” properties, right?

• Mixed properties
• Padding and margin properties
• Text properties
• Line properties
• Image properties
• Transition properties
• Scale properties

But then for LV_CHART_PART_BG and LV_CHART_PART_SERIES_BG is mentioned also "text style" and "Padding values" respectively "line style" and "padding values".
So do I understand it right that for LV_CHART_PART_BG can be applied:
• Background
• Border
• Outline
• Shadow
• Pattern
• Value
• + Text
• + Padding and margin
And for LV_CHART_PART_SERIES_BG can be applied:
• Background
• Border
• Outline
• Shadow
• Pattern
• Value
• + Line
• + Padding and margin

Kindly please confirm. Thank you.

Hi,

I appreciate the LittlevGL. Regarding the PC simulator, I have followed the steps and succeed in running make all. However, I got the following error.

make all
'Building file: ../lv_drivers/display/fbdev.c'
../lv_drivers/display/fbdev.c:17:10: fatal error: sys/mman.h: No such file or directory
#include <sys/mman.h>
^~~~~~~~~~~~

I can hardly find the "mman.h" in MinGW, SDL, and the simulator source itself. Would you help me to figure out this error?

Thanks,
Joshua

With the following code in place, my list does not function in the horizontal layout. I've tried numerous solutions found in other posts on issues here, with no luck. The only thing I can assume is that the LV_LAYOUT_ROW_M is broken/not working as intended for list objects.

My screen ends up looking like this:

This is being tested on a simulated version, not running on my actual embedded device (currently not possible as it is highly custom, display drivers still WIP).

Browsing to https://doc.littlevgl.com or http://docs.littlevgl.com now gives an invalid certificate error in my browser.

Documentation about lv_style_set_text_font isn't updated, it needs three arguments instead of the documented two.

From 7.0.1 docs.

Documentation still references lv_conf_templ.h, which was renamed in lvgl/lvgl@abfdfd1 to lv_conf_template.h.

• Create objects
• Multi screen
• Styling (button examples)
• Responsive, layout, fit
• Animations, style animations
• Monochrome
• GPU
• Rotate screen
• lv_task
• Internationalization (lv_i18n)
• bidi
• ext_data, signal/design_event_cb
• New obejct type

In the doc of lv_img (overview):
Image decoder interface is a dead link

I'm not a lawyer, but I think there are legal ramifications to using code snippets that are not licensed from documentation.

Is it possible to add a statement below the copyright saying that "Code snippets are licensed under the MIT license"?

l am using a listview widget in my design and I am going to change the color of the scrollbar?

how can I do that?

Padding and margin properties:
the properties (pad_top, pad_bottom, etc) are not bulleted.

Border properties:
The border in drawn on to of the background. => The border is drawn on top of the background. (please check if it's true)

Border properties:
border_post (bool): If true the border will be drawn all children has been drawn. => If true the border will be drawn when all children have been drawn.

Shadow properties:
shadow_spread: ake => make

Value properties:
values_str: Only the pointer is saved. => Only the pointer is saved! Don't use local variable with lv_style_set_value_str, else use lv_obj_set_style_local_value_str.

Transition properties:
transition_1 to transition_6: an other => another
Question: should be transition_prop_1? Because the macros are called lv_style_set_transition_prop_1 ...

These are all findings plus the questions

Hi
In the Style part of the documentation, not all of the properties has the default value.
For example, if we see the shadow part, only the shadow_blend_mode has the default value.
I think it's a good idea to write their default values. I have no idea how to get them easily. If you tell me I can help you with this.

The description on how to rebuild the docs is wrong. What do I have to do to rebuild the docs?

On the spinner docs the example creates a spinner widget named preload, from that point forward most of the spinner related functions talks about a preload object but I think it refers to the spinner instead.

Or should the spinner widget be renamed to preload?

From:

Functions

lv_obj_t *lv_spinner_create(lv_obj_t *par, const lv_obj_t *copy)

Create a pre loader objects

Return

    pointer to the created pre loader
Parameters

        par: pointer to an object, it will be the parent of the new pre loader

        copy: pointer to a pre loader object, if not NULL then the new object will be copied from it

void lv_spinner_set_arc_length(lv_obj_t *preload, lv_anim_value_t deg)

Set the length of the spinning arc in degrees

Parameters

        preload: pointer to a preload object

        deg: length of the arc

To:

Functions

lv_obj_t *lv_spinner_create(lv_obj_t *par, const lv_obj_t *copy)

Create a spinner object

Return

    pointer to the created spinner
Parameters

        par: pointer to an object, it will be the parent of the new spinner

        copy: pointer to a spinner object, if not NULL then the new object will be copied from it

void lv_spinner_set_arc_length(lv_obj_t *spinner, lv_anim_value_t deg)

Set the length of the spinning arc in degrees

Parameters

        spinner: pointer to a spinner object

        deg: length of the arc

Hi,
https://github.com/littlevgl/docs/blob/master/en/object-types/lmeter.md#range-and-angles

...default line number is 31.

in code

ext->line_cnt    = 21;  /*Odd scale number looks better*/

In both pdf and html, seems this picture "page_small.png" was not found (chapter 4.4.4: Overview > Styles > Parts)