I’m having trouble figuring out what’s wrong with my files for compiling. the initial errors are pointing to the .h and corresponding part in the keymap.c files but it seems fine to me? i haven’t even managed to get to figuring out the joystick part which is where i thought i would start having a bunch of trouble

Unsure the best way to show files but I don’t think copy pasting them into the body of this post would be best so I’ve uploaded here: https://drive.google.com/drive/folders/1WKobV73ZdovPCUUcp0jLBLaX8L6IFEmp?usp=drive_link

The txt file shows the error text I get when trying to compile

Thank you

  • dentonOP
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    9 months ago

    I’ve actually got all the code to work now except the joystick part, which is the biggest (new) part for me for this keeb. I’ve been on the QMK discord (that’s how I knew to update QMK to resolve QK_BOOT haha, although I’m not entirely sure the combo works…) What do you mean read the joystick input pins once per scan instead of in every if statement?

    edit: yeah config_common is deprecated according to the QMK discord. very unfortunately I actually have no idea what I’m doing with QMK/C++ code (esp the joystick part) in general and have just been kinda sticking things I’ve found on the internet in in hopes of something working out but no luck so far

    • obosob@feddit.ukM
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      9 months ago

      What I mean is in the matrix scan code you have multiple calls to analogReadPin(B5) and analogReadPin(B4). You used to just read it at the top of the function and store its value in a local variable. I’m suggesting to put that back.

      • dentonOP
        link
        fedilink
        arrow-up
        1
        ·
        9 months ago

        Ah ok got you, I’ve changed it back now.

        Do you have any idea why this might be happening?

        The joystick recognises UP correctly and just for the duration it’s pushed upwards.

        When pushed to the LEFT, it reads left but continuously goes left even when released.

        When pushed DOWN, it triggers left and down and continuously goes left and down even when released (when slowwwwwly pushed down, it reads left first, then down)

        when pushed to the RIGHT, nothing is recognised (when pushed up first then rolled over to the right, it recognises up and right/right once - inconsistent but most of the time it’s up and right, not just right)