LVGL v8 is available for testing!

kisvegabor · April 15, 2021, 8:26pm

Yes, the documentation is being updated.

Herve_14 · April 18, 2021, 6:33pm

Hi
I have tested some examples with V8 version ( i use Arduino Due & RA8875 with DMA SPI)
Demo_widgets works fine now, i still get a little bug with demo_keypad_encoder :

The message box open on the left side of then screen even if i change lv_obj_center(mbox); to lv_obj_align(mbox,LV_ALIGN_BOTTOM_MID,0,0);
All the widgets stay on the left side of the screen… but if i change LV_FLEX_FLOW_COLUMN in “lv_obj_set_flex_flow function” i can observe some changes but i can’t put the widget in the middle of screen…

Thanks

egonbeermat · April 20, 2021, 12:13am

A simple one - did I miss an “announcement” of what benefits v8 offers vs. v7?! I can’t seem to find that; I have been aware of its upcoming release on here, and even briefly tried to convert until the number of breaking changes put me off for a bit But is there a simple elevator pitch about what changed, whats new and better, whats gone, etc?

embeddedt · April 20, 2021, 1:40am

The “pitch” hasn’t been written yet, as there are indeed a number of breaking changes.

Herve_14 · April 20, 2021, 8:37pm

Hi,
I just tested the very last code and it’s ok now : no more bugs with Widget and Encoder examples… (i’ll test the others examples next week end)…
Very nice result, well done!!!
Best regards

CHNzyf · April 21, 2021, 7:26am

v8 It’s very comfortable to use.
Unfortunately why not the mouse over effect?,
Because I’m going to use it on my PC.

kisvegabor · April 22, 2021, 1:40pm

It’s on the roadmap, just not with top priority. It will come in v8.1 or v8.2.

Miguel_0101 · April 23, 2021, 2:51pm

I liked the keyboard layout.

sjpw · April 25, 2021, 7:42am

when V8 will release ?

Herve_14 · April 25, 2021, 5:48pm

Hi

I continued testing version 8 today (yersterday 's version):

Demo_Widget is ok but it use 98% of the Due flash memory (lot of .c pictures!)… and i have 30k of free sram for an application…
Demo_Encoder : no problem
Demo_Benchmark is ok (w/ poor but common results!!)
Demo_Stress_ : everything is ok except the test w/ dropdown (case 11: ) lv_dropdown_open(obj) crash the code

I didn’t test Demo_Music because it doesn’t fit in the due flash.

I also tested the Lv_File_system and .bin image from SD Card : it’s ok … (i think it’s a good solution to save flash memory).

Regards

embeddedt · April 25, 2021, 6:12pm

I agree that demo_widgets has high flash memory usage. The simplest solution is probably to add a “low memory” option that reduces the number of font sizes being used (there are many right now) and also disables the images.

kisvegabor · April 27, 2021, 11:23am

I’d rather check if the font is enabled and if so use it. If not, print a warning and use a default font.
The problem is that the widget demo now uses 3 times more fonts because the display size is set in run time and the fonts need to be enabled for all screen sizes.

See here:

github.com

lvgl/lv_demos/blob/76f64890a0387a48f72eb79d556a4324a62841b9/src/lv_demo_widgets/lv_demo_widgets.c#L103-L124


      
          if(disp_size == DISP_LARGE) {
              tab_h = 70;
              font_title     =  &lv_font_montserrat_28;
              font_icon      =  &lv_font_montserrat_24;
              font_subtitle  =  &lv_font_montserrat_24;
              font_normal    =  &lv_font_montserrat_16;
              font_small     = &lv_font_montserrat_12;
          } else if(disp_size == DISP_MEDIUM) {
              tab_h = 60;
              font_title     =  &lv_font_montserrat_22;
              font_icon      =  &lv_font_montserrat_18;
              font_subtitle  =  &lv_font_montserrat_18;
              font_normal    =  &lv_font_montserrat_14;
              font_small     = &lv_font_montserrat_10;
          } else { /* disp_size == DISP_SMALL */
              tab_h = 50;
              font_title     =  &lv_font_montserrat_22;
              font_icon      =  &lv_font_montserrat_16;
              font_subtitle  =  &lv_font_montserrat_16;
              font_normal    =  &lv_font_montserrat_12;

This file has been truncated. show original

embeddedt · April 27, 2021, 12:59pm

Yes; that’s an issue. I wonder if we can reduce the number of fonts being used by the demo when they aren’t enabled. Maybe we should just have a normal font and small font for each display?

juneofive · April 28, 2021, 6:52am

I had the pleasure of running V8 on VS Studio. I ran some of the widget examples and found that some of the widgets were much improved and enhanced(APIs) over V7, but I didn’t fully grasp them yet, so I was looking forward to the documentation.

kisvegabor · April 28, 2021, 8:18am

I’ve improved the font usage. Now every screen size uses only 2 fonts instead of 4.
A fallback is also added to LV_FONT_DEFAULT if a font is not enabled.

kisvegabor · April 28, 2021, 8:18am

Great! Looking forward to hear your feedback!

juneofive · April 28, 2021, 2:25pm

I’ve just tested the Meter example3, the analog clock, which is much more powerful and easier to use than V7.At the same time, I also found several problems (maybe my method is wrong).

1 The order of layers in the needle is based on the order in which the scale was created, not the order in which the needle was added.
2 After IMG was used to add the needle, there was still a black dot in the center.I think in general we wish it didn’t exist, but I haven’t found a way to remove it yet.
3 In some cases the needle layers get out of order. My original order is hour->;min->SEC (bottom to top), when I only update min and hour, changes to min- >;hour->sec
4 IMG is very serrated when rotated to a non-horizontal or vertical Angle.
5 I want to set the defalt theme to dark and change the define in LV_conf. H like this

/ * 1: Light mode;0: Dark mode*/

# define LV_THEME_DEFAULT_PALETTE_LIGHT 0

but it didn’t work.

that’s all.if you found i have go a wrong way, please tell me konw.

By the way, I plan to make a watch with the following effect based on meter.I haven’t found an artist to help me design the images. I guess I’ll have to learn Photoshop, but it’s in my plans anyway.I will share it with you here when it is finished.
https://img.zcool.cn/community/01cba56086857a11013e3b7d71d727.gif

embeddedt · April 28, 2021, 2:30pm

I also ran into that issue and fixed it in master; please pull again and it should work. (Update: since my commit the define name has been changed to LV_THEME_DEFAULT_DARK and the number was inverted.)

It might be a limitation of having a 1-pixel thick needle, as I can’t think of a simple way to keep the thickness equal between angles that are multiples and not multiples of 90 degrees. FWIW I’ve seen this issue occur in browsers as well when rotating images.

The best workaround is probably to use a thicker needle so the effect is less obvious.

juneofive · April 28, 2021, 2:43pm

Thank you so much for replying to me so soon, I will try.Do you have a good solution to my second question? Because when making a needle with an image, we usually design the center mark on the needle image, so the extra center black dot will look inconsistent and destroy the original design effect.

embeddedt · April 28, 2021, 2:47pm

I haven’t tested it, but from reading through the meter code, setting bg_opa to be transparent on the gauge’s LV_PART_INDICATOR should work.