• 9 Posts
  • 77 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • 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)


  • 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


  • I’ve tried to rewrite the joystick code and now am getting different errors:

    Compiling: quantum/keymap_introspection.c                                                           [OK]
    Compiling: quantum/command.c                                                                        [OK]
    Compiling: tmk_core/protocol/host.c                                                                tmk_core/protocol/host.c: In function 'host_joystick_send':
    tmk_core/protocol/host.c:171:10: error: 'report_joystick_t' {aka 'struct '} has no member named 'axes'
             .axes =
              ^~~~
    tmk_core/protocol/host.c:172:13: error: extra brace group at end of initializer
                 {
                 ^
    tmk_core/protocol/host.c:172:13: note: (near initialization for 'report')
    tmk_core/protocol/host.c:172:13: error: excess elements in struct initializer [-Werror]
    tmk_core/protocol/host.c:172:13: note: (near initialization for 'report')
    cc1: all warnings being treated as errors
     [ERRORS]
     | 
     | 
     | 
    gmake[1]: *** [builddefs/common_rules.mk:361: .build/obj_eiris_default/protocol/host.o] Error 1
    gmake: *** [Makefile:392: eiris:default] Error 1
    Make finished with errors
    

    Also, I’m not sure if I need "#include “config_common.h” in my config.h file? I see it in some other config.h files. When I have that in my config.h file, it gives a fatal error: No such file or directory









  • I haven’t started experimenting around with the code for joysticks but am in the middle of making a keyboard (half) with a joystick. Did you find it worked ok just for acting as keyboard keys/combinations of keys?

    I see under the ‘Accelerated’ portion where you tried to emulate mouse keys there weren’t really any results?


  • If you’re talking about long term working out, motivation will not cut it. It has to be determination/making it a habit. Like - “Time to take a shower”, “time to workout”.

    But working out doesn’t mean you have to push yourself till you feel like puking. Start small, do 10 squats at lunch and another 10 when you finish your work day for e.g… Do something you find fun, not something that’s just “well running is exercise so I guess I have to do that”






  • ‘Feed’ like Facebook feed or twitter feed or whatever social media feed. I guess mostly for the same reason as OP’s. It makes people sound like brainless zombies just grazing on whatever is ‘fed’ to us by advertisers/whatever the platform has been paid to push .




  • I used the 2 and currently use the 4a (coming up to 3 years this Oct) but I think that’s the end of the line for me on pixels cause they’re just getting too big for someone with really small hands.

    My three wants (in order or priority) for phones are: 1) reasonably small enough (pixel 4a just about fits into this criteria); 2) fingerprint scanner; 3) headphone jack

    I’ve got a tiny jelly star from unihertz coming and if that doesn’t work out I’ll probably have to go zenphone cause they’re just about the size of the 4a.

    Pity as I do like the pixel line











Moderates