Navigation

    M5Stack Community

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. chama
    C
    • Continue chat with chama
    • Start new chat with chama
    • Flag Profile
    • Profile
    • Following
    • Followers
    • Blocks
    • Topics
    • Posts
    • Best
    • Groups
    Save
    Saving

    chama

    @chama

    0
    Reputation
    2
    Posts
    64
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    chama Follow

    Posts made by chama

    • RE: CoreS3 virtual buttons

      Hello @felmue
      Thank you for reading my bad English.
      And the idea of touching the lower rim of the display is good.

      However, it is a mystery whether there is a built-in sensor only at the position of the microphone hole at the bottom left.

      The documentation I wrote in the first post can be found on this page ( https://docs.m5stack.com/en/core/CoreS3 ) under the link "CoreS3 User Guide".

      The direct link is here ( https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/docs/products/core/CoreS3/CoreS3 Development Kit-compressed (1).pdf ).

      Thanks
      chama

      posted in Cores
      C
      chama
    • CoreS3 virtual buttons

      Page 7 of the CoreS3 document "CoreS3 Development kit.pdf" contains the following information.
      **
      Covering most of the from is the capacitive multitouch screen sensor with three dedicated touch zones available in code as buttons A, B and C.
      These are not clearly marked as zone A shares the same location and the left microphone,
      Zone B shares the same location as the camera and zone C shares the same location as the right microphone.
      **
      However, there is no mention of CoreS3 in the comments on M5Unified's Button.ino.
      I actually tested Button.ino and it doesn't work.
      That's why I thought CoreS3 was not equipped with virtual buttons.

      But when I test the code below,

      #include <Arduino.h>
      #include <M5Unified.h>
      void setup() {
         auto cfg = M5.config();
         M5.begin(cfg);
      }
      
      void loop() {
         M5.update();
         if(M5.Touch.isEnabled()){
           auto t = M5.Touch.getDetail();
           auto p = t.isPressed();
           auto r = t.isReleased();
           auto h = t.isHolding();
          
           auto x = t.base_x;
           auto y = t.base_y;
           M5.Display.setCursor(0,0);
           M5.Display.setTextSize(2);
           M5.Display.printf("x=%4d y=%4d PRH=%d %d %d",x,y,p,r,h);
         }
         delay(1);
      }
      

      When you touch the Zone A area, x=80, y=2000 will be displayed.
      Pressed Released Holding is also displayed correctly. In other words, it seems that only button A is implemented.
      When I touch Zone B or C, it doesn't respond at all.

      What does this mean?
      Is there any official comment on this?

      posted in Cores
      C
      chama