hello,
i use the nice lvgl Lib to do That.

create personalized button add event on the button

example :

from m5stack import * from m5stack_ui import * from uiflow import * import lvgl as lv screen = M5Screen() screen.clean_screen() screen.set_screen_bg_color(0x00000) lv.init() # create screen scr = lv.obj() # set Background screen scr.set_style_local_bg_color(scr.PART.MAIN, lv.STATE.DEFAULT, lv.color_hex(0x000000)) # create button btn = lv.btn(scr) btn.set_size(80, 80) # change style btn.set_style_local_bg_color(scr.PART.MAIN,lv.STATE.DEFAULT, lv.color_hex(0x0000ff)) styleButton = lv.style_t() # create style styleButton.set_bg_color(lv.STATE.DEFAULT, lv.color_hex(0x0000ff)) styleButton.set_radius(lv.STATE.DEFAULT, 0); styleButton.set_border_color(lv.STATE.DEFAULT, lv.color_hex(0x0000ff)) btn.add_style(btn.PART.MAIN,styleButton) #define this style # callback action def action(btn, event): global src if(event == lv.EVENT.CLICKED): btn.set_style_local_bg_color(btn.PART.MAIN, lv.STATE.DEFAULT, lv.color_hex(0xffffff)) btn.set_style_local_border_color(btn.PART.MAIN, lv.STATE.DEFAULT, lv.color_hex(0xffffff)) # define callback btn.set_event_cb(action) # load the screen lv.scr_load(scr)

best regards
Thomas

Hello @Robertolo

if you look at the M5Core2 schematic in the top left corner you'll find AXP192 and its inputs ACIN (connected to USB_5V) and VBUS (connected to BUS_5V). USB_5V comes from USB and BUS_5V comes from the LAN module.

The AXP192 automatically switches between the available power sources and picks the one best suitable. Please also check the AXP192 datasheet.

Thanks
Felix

OK - I had to find my ownn solution to this:

The problem lies with using the loop to run all the updates. If you do that - and manage your program from the loop then you need to use globally declared instances of all the buttons. If you try and create button ways dynamically via procedure they are scoped within that procedure - and they are disposed of automatically (whether you like it or not!!) when you exit the function/procedure and return to the Loop.

SO

I only use the Loop for switch case statement to invoke the loopProcedure for each given page.

I create a mode variable currentPage, and a dedicated loopProcedure for every page of the project (loopMainMenu, loopPlaybackPage etc. etc.)

Each loopProcedure draws the screen, invokes the necessary buttons and handlers for that page locally, and then starts a local do-while (currentPage=loopMainMenu){} loop to provide all the typical loop based functions like m5.update(); to keep the button system ticking and battery management going for that page. It stays in this while loop until the back button is pressed or the system navigates to another page somehow (by repointing the currentPage variable).

It is the button handler functions that can then change the page which cause the while loop to exit back to the main Loop - and the entire loopProcedure then disposes of everything related to the old page, and a new page loopProcedure is then invoked through the switch case statement in the Loop.

It's a bit clunky because I would prefer that the library itself simply supported dynamic disposal and invokation of global objects - and having a loop for each page is going to get quite bloaty quite quickly but wit ha little care and some carefully designed functions we can reuse most of the code not related to button invokation.

I'm not able to post any code I'm afraid - but it works and you can leave some global buttons like button C is my back button and that wil never change, buttons a and b are also global (but all could be defined locally if required).

I hope that helps someone in the future.

thanks for the help @felmue - ive got it working now - i think i must have been pretty tired because I have no idea how all 3 attempts failed.

It works with .waspressed and by attaching a handler to events for the M5.BtnA - I have no idea what I was doing wrong all 3 times.

I found one issue - it was a silly mistake in my handler logic :D but this does not explain .ispressed not working before.

Maybe its something to do with a lack of sensitiviity as well - but the important thing is - they do work and I've got it working.

But trying to make a button bigger all the way down to 280 does not seem to work - which is a shame becasue I have to make 2 declarations to the handler. but thats ok.

Thank you

@mb

The m5button engine supports swipe gestures and the sprite engine can animate your graphics.

Not aware of any m5 animation engines that handle that but maybe have a look at the Raphael animation engine - its very neat and might inspire you to port it for m5 sprite.

Could also look at bounce.js - the maths to calculate easing is not complicated.

Try to replace

M5.Rtc.SetData(&RTC_DateStruct);
with
M5.Rtc.SetDate(&RTC_DateStruct);

it worked for me.

Thanks again @world101

I have seen it. But I think it would have to be in the model documentation, if it is I missed it.

Have a nice day
Carles

Thank you very much!

Hi @felmue , thanks for your input, I was almost there, but wanted to be sure I had to remove the old battery and not needed to connet the one in M5Go.

Similiar problem here - Ill start a new thread in case its a different issue

Hello @wa-berlin

you can't. Functions w/o numTimer argument will return the internal number assigned to a specific timer. You don't have direct control about which timer gets which number, but you can keep a record of the number assigned to a given timer to further manipulate it.

Below is an example with 2 timers (A and B). Timer A counts up ever 2 seconds, whereas timer B counts up every second and stops at 10.

With button A you can enable and disable timer A.
With button B you can restart timer B once it has stopped.

#include <M5Core2.h> #include <utility/M5Timer.h> M5Timer M5T; int mytimerA = -1; int mytimerB = -1; int mycountA = 0; int mycountB = 0; void myTimerACB(void) { mycountA++; } void myTimerBCB(void) { mycountB++; } void setup() { M5.begin(); M5.Lcd.setTextSize(3); mytimerA = M5T.setInterval(2000, myTimerACB); mytimerB = M5T.setTimer(1000, myTimerBCB, 10); } void loop() { M5.update(); M5T.run(); if(M5.BtnA.wasPressed() == true) { if(M5T.isEnabled(mytimerA) == true) { M5T.disable(mytimerA); } else { M5T.enable(mytimerA); } } if(M5.BtnB.wasPressed() == true) { if(M5T.isEnabled(mytimerB) == false) { M5T.deleteTimer(mytimerB); mycountB = 0; mytimerB = M5T.setTimer(1000, myTimerBCB, 10); } } M5.Lcd.setCursor(0, 0); M5.Lcd.printf("Timer A: %s\n", M5T.isEnabled(mytimerA) ? "enabled " : "disabled"); M5.Lcd.printf("Timer A: %04d", mycountA); M5.Lcd.setCursor(0, 100); M5.Lcd.printf("Timer B: %s\n", M5T.isEnabled(mytimerB) ? "enabled " : "disabled"); M5.Lcd.printf("Timer B: %04d", mycountB); }

Good luck!
Felix

It is definitely something to do with the size of the program. Once it reaches a certain size it will no longer run. All I have to do is delete anything (reducing the size) and it will run again. I provided a sample of my code to tech support and they are working with engineering to investigate.

Here we go, easy work-around the faulty lcd.image():

from m5stack import * buffer = open("/sd/images/test.jpg").read() lcd.image_buff(lcd.CENTER, lcd.CENTER, buffer)