yowkees / keyball Goto Github PK
View Code? Open in Web Editor NEWkeyball is split keyboard has 100% track ball
License: GNU General Public License v3.0
keyball is split keyboard has 100% track ball
License: GNU General Public License v3.0
Hi, I followed the tutorial for keyball44.
I'm in the testing part. I can't make the left PCB (the one without trackball) to work.
I can write the hex on the pro micro, so that makes sure it works; but I just don't know what else could I do to test. I finished the trackball right hand side and everything works correctly.
Any tips would be helpful ð
This are the things I did:
I also sent an email through the contact mail from shirogane-lab.com if you need more information from the purchase I can provide.
Thank you!
ããŒã«ã®ããåŽã ããUSBã«ã€ãªãã§
TRSãã€ãªããªããšããŒã«ãåå¿ããªãã
ã·ãªã¢ã«éä¿¡æååŸã«å
åŠã»ã³ãµãŒãã¹ãã£ã³ããŠããããšãåå ã
TRSãç¹ãã§ããªãå Žåã¯ã·ãªã¢ã«éä¿¡ã決ããŠæåããã¹ãã£ã³ããªãã
ã¹ãã£ã³ããŠããã·ãªã¢ã«éä¿¡ãããããã«å€æŽããã
ãŸãããŒã«ã®handnesså€å®ãåé¡ã§å·Šã®çåŽã ãã ãšãã€ã³ã¿ãåããªãã®ã䜵ããŠä¿®æ£ããã
ææ°ãã¡ãŒã ãŠã§ã¢ã«ãŠã¬ã€ã€ãŒïŒãžã®åãæ¿ããåºæ¥ãŠããªãããç¥ããŸããã
ã¬ã€ã€ãŒïŒã¯RGBã®å€æŽã®ä»ããã©ãã¯ããŒã«ãã¹ã¯ããŒã«ã«å€ããæ©èœãæã£ãŠããŸãã
ããã©ã«ãããŒãããã§ã¯å·Šæ芪æã®äžçªå
åŽã®ããŒã«å²ãåœãŠãããŠããŸãã
ã確èªããã ããã°å¹žãã§ãã
補é æã®åäœå·®ã»èª€å·®ãããããŸããã
PCBäžã®LEDã®ããŒãã³ã°ããããã«è¿ãå€å¥ãã«ããã£ãã§ãã
察åŠæ³ãšããŠã¯ä»¥äžãèããããŸãã
VIA察å¿ãããããã«ãå³ããçãšå·Šããçã®jsonãã¡ã€ã«ãäœæããŸããã
VIAãèµ·åããéã«èªåã§ã©ã¡ããæ¥ç¶ãããŠãããå€å¥ããæ¹æ³ãšããŠãPRODUCT_IDïŒ0001ãªãå³ã0002ãªãå·Šãšå€å®ããããšèããŠããŸãã
ä»ã¯makeåã«rev1/config.hã®äžãïŒâïŒãšæã§æžãæããŠããŸããããããèªåã§åãæ¿ããããã«PRODUCT_IDã®äœçœ®ãå€æŽã§ãããšå¬ããã§ãã
ãããå¥ã®ã¢ã€ãã¢ãããã°ãææ¡ããã ããã°ãšæããŸãã
ãæ€èšããã ããã°å¹žãã§ãã
LEDã®ç¹ç¯é åº(é ç·é åº)ããã«ãã¬ã€ãäžã«æ瀺ããŠãããšå©ãããŸãã
SK6812mini-Eã¯æ
£ãããšãã³ãä»ãã®å€±æãããããããŸããã
éã«èšãã°æ
£ããªã人ã¯ãã¯ã倱æããŸãã
ãã®ãããªæã«çªå·ããµã£ãŠããã°
ã©ã®LEDã«åé¡ãããã®ããäŒãããããªããŸãã
ãŸãå°ãæ
£ãã人ã§ããã°é
ç·é åºããããã°
ãããããšã«äžè¯åæãæšå®ã§ãèªå·±è§£æ±ºãããããªãã§ãããã
ãã©ãã¯ããŒã«ã±ãŒã¹ã«ãšããã·æ¥çå€ãä»ããæã«
æ¥çå€ãéæããã£ãçœãªã®ã§
ä»ãããã©ããéåžžã«åããã«ããäžå®ã§ããã
ã¡ãã£ãšèª¿ã¹ããšã¬ãžã³çšã®çè²å€ãªã©æ²¹æ§ã®ãã®ãšçžæ§ãè¯ã ããã§ãã
äœãããããèæ
®ãããšæ¥çå€ãçè²ãããšãããªãã·ã§ã³ã«èšåããã®ãè¯ãã®ã§ã¯ãªãã§ããããã
There are no English doc that Keyball46 uses different firmwares on sides w/ or w/o ball.
One reports me that auto shift does't work correctly in Windows's remote desktop with Keyball61.
And I found an issue in QMK qmk/qmk_firmware#13708
It says TAP_CODE_DELAY
work for the case.
But I don't try it yet.
Additionaly, there are some version inconsistencies in the issue.
It says 0.13.x has issue. But I verified that 0.15.x is not affected, and 0.16.x is affected again.
Anyway, it would be better to start TAP parameter adjusting.
When landing on the repository, there are no images in the README.md, so it is difficult to understand at a glance what the keyboards are like. It would be very helpful to have pictures embedded in the readme.
The last qmk version which works well with my keyball39 is 0.17.9.
There are some minor changes needed to compile with qmk 0.18.0, e.g., RESET to QK_BOOT migration, but I still managed to compile keyball firmware with qmk 0.18.0. However, after flashing the firmware, the movement of the trackball is not recognized at all. Maybe it's related to the pointing device improvements mentioned in the changelog.
Why update?
There would be a nice feature coming in the next breaking release of qmk that allows automatically activate the mouse layer when the mouse cursor is moved (qmk/qmk_firmware#17962).
Btw, as #126 pointed out, SAFE_RANGE
has been changed. From my experience, the special keycodes of keyball should be +1
(e.g., 0x5DA5
-> 0x5DA6
) in qmk 0.16.x. And it should be +8
(e.g., 0x5DA5
-> 0x5DAD
) in qmk 0.17.x.
The provided DXF files are (per design) untiless. They do not seem to be in millimeters nor inch. What is the unit of these files?
https://twitter.com/Ryo46671803/status/1414767783083008002
å·Šå³ã¯ãªãã¯ãèšå®ã§ããªãð
ãMouse Btn1ããšãMouse Btn2ããèšå®ããŠãå®è¡ãããªãã
ãµã€ãºåæžã®ããã«MOUSEKEYãç¡å¹ãªã®ã§
KC_MS_BTN1~8 (=KC_BTN1~8) ã解éãããŠããªãã
代æ¿ãšããŠèªåã§KC_MBTNãå®çŸ©ããŠãã
ããã§ã¯VIAãªã©ã§èšå®ã容æã§ã¯ãªãã
ããããVIAã¯KC_BTNãèšå®ããŠãããšæšæž¬ãããã
ãªã®ã§KC_BTNãç¬èªã«è§£éããã°å¯Ÿå¿ã§ããã¯ãã
ä¿®æ£ã®ããã®åèã³ãŒãã
ãŸã ãã¹ãã¯ããŠããªãã
While hacking on the firmware of my keyball61, I have seen that there are a few components that are self-implemented. Remarkable this is the support for the pmw3360 sensor and the mouse key handling. Is there any reason why these are implemented differently from what upstream QMK provides?
I have managed to build a firmware using the upstream drivers. It looks like it"s working fine. Is there interest in a pull-request for such a change?
In addition I would like to to see support for the keyball boards in upstream QMK. I think that would simplify firware builds and increases visibility of these great keyboards.
I found that it failed to compile firmwares with QMK 0.15.x when working on #75
Hi, thank you for submitting the review request for this keyboard. However, we have rejected the request, because the PRODUCT value does not match the value written in the config.h
file. For instance, you filled Keyball64
in to the review request form, but the value in the config.h
file is keyball
. You need to fill keyball
in to the review request form, or you need to change the PRODUCT value in the config.h
file to Keyball64
. Then, please resend the review request.
ããã«ã¡ã¯ããã®ããŒããŒãã«ã€ããŠã¬ãã¥ãŒç³è«ãéã£ãŠããã ããŸããŠãããããšãããããŸãããããããã®ãªã¯ãšã¹ãã¯æ¢ã«ãªãžã§ã¯ããããŠããã ããŠãããŸããçç±ãšããããŸããŠã¯ãPRODUCTå€ã config.h
ãã¡ã€ã«ã«æžãããå€ãšäžèŽããŠããŸãããå
·äœçã«ã¯ãã¬ãã¥ãŒãªã¯ãšã¹ããã©ãŒã ã« Keyball64
ãšèšå
¥ãããŠããŸãããã config.h
ãã¡ã€ã«å
ã®å€ã¯ã keyball
ã§ãããã¬ãã¥ãŒãªã¯ãšã¹ããã©ãŒã ã« keyball
ãšèšèŒããŠããã ãããããã㯠config.h
ãã¡ã€ã«å
ã® PRODUCT å€ã Keyball64
ã«å€æŽããŠããã ãå¿
èŠãããããŸãããã®åŸãã¬ãã¥ãŒãªã¯ãšã¹ããåéä¿¡ããŠããã ããŸããšå©ãããŸãã
ããã¯ãã¡ãŒã ãŠã§ã¢ã®çæã§è§£æ±ºãããããšãããããŸãããã
çŸåšã¯ãã©ãã¯ããŒã«ãããæ¹ãmaster(=USBæ¥ç¶ããã)ã«ããªããã°
ãã©ãã¯ããŒã«ãæ©èœããŸããã
ãã®ããšããã«ãã¬ã€ãã«æžããŠããã°ã
ããå®æããŠãã©ãã¯ããŒã«ããã¹ãããŠã¿ãã
ãšãªã£ãæã®ãã©ãã«ãæžããšäºæ³ãããŸãã
related #18
ä»ã® LAYOUT
ãã¯ãã«ã¯ããã€ãåé¡ãããã®ã§ä¿®æ£ããã»ããè¯ãã§ãã
ä¿®æ£å
容ã¯ä»¥äžã®éãã
å³åŽããŒã«ãå·ŠåŽããŒã«ãããã«ããŒã«ãããŒããŒã«(ãããã?)ã®æ§æã«åããŠãããã LAYOUT ãçšæãã
åœåäŸ: LAYOUT_rightball
, LAYOUT_leftball
, LAYOUT_doubleballs
, and LAYOUT_noballs
LAYOUT
ã LAYOUT_rightball
ã®ãšã€ãªã¢ã¹ãšãã
åã¬ã€ã¢ãŠãã§å²åœäžå¯èœãªããŒé ã
äŸ: å³åŽããŒã«ã«ãããå·Šã® F6, B5 ãš å³ã® F7, B5
handiness ã®èªåå€å®ãèæ ®ãããšäœ¿ããªãããŒã«ã¯ããŒããããèšå®ã§ããªãã»ãè¯ãã
LAYOUT_kc
ã®å»æ¢
MO(1)
ãªã©ãèšè¿°ããã®ã«ãããã KC_*
ãªããŒã³ãŒããå®çŸ©ããå¿
èŠããããQMKã®æµåãšã¯èããç°ãªããå€å°æéã§ã KC_Q
ãªã©ã¯ãã®ãŸãŸæžããŠãããæ¹ãè¯ããqmk c2json ã json2c ã®ããšãèãããšããŸãè¯ãã¢ã€ãã¢ãšã¯èšããªãã
LAYOUT_kc
ã䜿ã£ãŠãããŒããããåè¿°ã® LAYOUT_rightball
ããã㯠LAYOUT
ã䜿ã£ããã®ã«çœ®ãæããããŒã«ã®æç¡=åºæ¿ã®çš®é¡ã§2çš®é¡ã®ãã¡ãŒã ãäœãã
åå㯠rev1/ball ããã³ rev1/noball ãšããã
ããã«å
ç«ã¡ LAYOUT
ã®æŽçãããã»ããè¯ãã
ããã«ã€ããŠã¯å¥é issue ãäœããŸãã
Originally posted by koron June 21, 2021
ããŸããŒã«ã®æç¡(åºæ¿ã®éã)ã«ããããã¡ãŒã ã¯1çš®é¡ã§ããããããåããã»ããè¯ãã®ã§ã¯ãªãããšã®ã¢ã€ãã¢ãåŸãŸãããæèã®æšç§»ã¯ä»¥äžã®éãã§ãã
å·Šå³èªåå€å®ãããŒã«ã®æç¡ã®èªåå€å®ããããã
ããŒã«ã®æç¡ã®èªåå€å®ã¯äœããã®æ¹æ³ã§ã§ããã (PMWã«ResetãªããŠã¬ã¹ãã³ã¹ãèŠãŠã¿ã)
å·Šå³ã®èªåå€å®ã¯ç¡çãã
ProMicroã®æªäœ¿çšãã³ããªã & ç°ãªãåºæ¿ã§æªäœ¿çšãããªãã¯ã¹ãç°ãªãããã1çš®ã®ãã¡ãŒã ã§2çš®ã®åºæ¿ã®å·Šå³ãå€å®ãã(4éã!)ã»ã©ããæ段ããªããããŒã«ã®æç¡ãå€å®ããã®ã¡ãããã«å¿ããŠãã§ãã¯ããæªäœ¿çšãããªãã¯ã¹ãå€ããããšã¯ã§ããããã ãâŠè€éã§ããŸã奜ãŸããã¢ã€ãã¢ãšã¯ãããªãã
ãªããã£ãPCBæ¯ã«å¥ã®ãã¡ãŒã ãçšæãããã©ãã(ååã®äŸ: rev1/onball
, rev1/offball
)
ååã¯ããšã§å€æŽå¯
ãããªãæªäœ¿çšãããªãã¯ã¹ã§å·Šå³å€å®ã§ãã
ãã¡ãŒã ãŠã§ã¢ã®ãµã€ãºåæžã«ãã€ãªããäžç³äºé³¥
offballã¯PMWã®ãã¡ãŒã ããŸããŸãèŠããªããªã(倧ããªå¹æ)
onballã¯ãã©ãã¯ããŒã«ã®æç¡å€å®ãèŠããªããªã(å°ããªå¹æ)
offballã«ã ãviaãå ¥ããŠUSBãç¹ã(masterã«ãã)ããã«ãããšãonballããviaãæ¶ããŠãã¡ãŒã ã«äœè£ãã§ããã®ã§ã¯?
VIAã¯USBãç¹ãã§ãã»ãã ãã§è¯ãã¯ããTRRSã®éä¿¡å 容ã¯ãããªã¯ã¹ã®è»¢éãRGB LEDã®ã¿ã€ãã³ã°åæã ãã§VIAåºæã®ãã®ã¯ãªã
å€å®ã«äœ¿ããããªã¯ã¹ã¯ onball ã F7, B5
㧠offball ã F6, B5
ãäºå®
rev1
ã¯åŒãç¶ãèªåå€å®ãªãããã©ãã¯ããŒã«åŽã«USBãæ¥ç¶ãã&å·ŠæããŒã«ã®å Žåã¯é©åãªãã¡ãŒã ã䜿ããã§äœ¿ãã
@koron æ§
å
¬éãããŸããKeyball61ã®VIA察å¿ãã¡ãŒã ãŠã§ã¢ã䜿çšããŠã¿ãŠã®ãææ¡ã«ãªããŸããREMAPã䜿çšããŠã¿ãŸããã
æ°ãããã¡ãŒã ãŠã§ã¢ã§ã¯ã"SCRL_MO"ãè¿œå ããããããæŒäžäžã«ã¹ã¯ããŒã«ã¢ãŒãã«å
¥ãããšãç解ããŸããã
ç§ã以åãã䜿ãæ £ããããŒé åã§ããšãå·Šæ芪æããŒã®å€åŽããŒã¯ãHOLDã§Layer3ïŒscrollã¢ãŒãã«ãªããTAPã§ããªå ¥åã«ãªãããã«äœ¿çšããŠããŸããããããšåãããŒé 眮ã«ããããšè©Šãããšããã"SCRL_MO"ã¯HOLDã«èšå®ã§ããªãããã§ãã@yoichiro ããã«äŒºã£ããšãããHOLDã«æå®ã§ããããŒã¯QMK_FirmwareåŽã§éå®ãããŠãããããªãããšã®åçã§ããããåºæ¥ãªãããã§ãã
ããã§ãæ°èšã®"SCRL_MO"ã¯æ®ãããŸãŸãLayer3ã«åãæ¿ãäžã«Scrollã¢ãŒããšãªãä»æ§ã埩掻ãããã®ã¯ã©ãã§ããããïŒ
ããããLayer3ãšã¹ã¯ããŒã«ã¢ãŒãã®é£åã§åé¡ãçºçããããã«"SCRL_MO"ãæ°èšããããšãããããªäºæ
ãããããã§ããããäœæŠèããããšæããŸãã®ã§ãæãããã ããã°å¹žãã§ãã
倧å€ãææ°ã§ããããæ€èšããã ããã°å¹žãã§ãã
because https://remap-keys.app/docs/support-qmk-022
previous work: #183
related issue: #314
planned QMK version: 0.22.3
I want to try to build a hand wire Keyball44 but i cannot find the stl for the trackball mount. Where i can found it?
Keycodes which described in the document may wrong.
It come from difference of QMK version, which fimwares linked with.
Keyball expected QMK/0.16.3.
But latest QMK is 0.17.0.
And SAFE_RANGE
is changed at this commit qmk/qmk_firmware@68c04ee
It changes values of Keyball defined keycodes.
These really should be PRed to upstream QMK.
If you need any help with that, I'd be more than willing to help out.
ã¿ã€ãã«ãå€æŽããããŸããã
keyball61ã賌å
¥ããçµã¿ç«ãŠãå®äºããŸããã
äžéãåé¡ãªã䜿ããŠã¯ããã®ã§ãããäžå®æéïŒ30åã»ã©ïŒäœ¿ã£ãŠãããšããã©ãã¯ããŒã«ã®é床ãååãããã«ãªã£ãŠããŸãããšãé »çºããŠããŸãã
ãã®åºŠã«ãresetãè¡ããšãå ã®é床ã«æ»ãã®ã§ããããã¡ãã®åå ã¯äœãå¿åœããããããŸãã§ããããïŒ
ãããããé¡ãããããŸãã
ããŒæäœãšé£åãã LED ã¢ãã¡ãŒã·ã§ã³ãå©çšããããšãå¯èœã«ãªããŸãã
RGB_MATRIX_ENABLE = no # Enable RGB_MATRIX (not work yet)
rules.mk ã«ãæžãããŠãããšããçŸç¶ RGB_MATRIX ãžã®å¯Ÿå¿ãæªå®è£ ã ãããŸããŸæåäŸãçºèŠããŸããã®ã§å ±æããŸãã
USBããã«æ¥ç¶ããŠäœ¿ãããšããŠãããã¹ãŠã®ããŒãšãã©ãã¯ããŒã«ãåäœããŸããã
USBããã䜿ãããPCã«çŽæ¥ç¹ãã ãtypeC-typeAå€æã±ãŒãã«ã«ç¹ãã ããããšãæ£åžžã«åäœããŸãã
æ®éã®ããŠã¹ã¯ãã®USBããã«æ¥ç¶ããŠãåäœããŸãã®ã§ãUSBããã®åé¡ã§ã¯ãªããšæããŸãã
éåžžç¹ãã æ¹ã®Keyballã«ã¯ããŒãããŒã«ã®æ å ±ã衚瀺ããããšæããŸãããUSBããã«ç¹ããšKeyballã®ããŽã衚瀺ãããŸãããã®çŸè±¡ãšé¢é£ãããæ°ãããŸããããããã§ããããïŒ
The QMK configuration in this repository is implemented using a QMK version from 2-3 years ago. It does not work with the current version of QMK.
For users that have advanced QMK configuration, they have to compile the firmware from source, instead of REMAP/VIA. This is currently not possible unless we drop down to a much older version of QMK.
Is it possible to update the QMK config to be compatible with the newer versions of QMK? Starting point would be defining a info.json
file. Thanks!
PS. I believe QMK now supports pmw-3360 out of the box.
Bottom acrylic, mid PCB is there. But, no top PBC/acrylic.
衚瀺ããããã®
printf ã䜿ã£ã¡ãããšãã¡ãŒã ãµã€ãºãããªãå¢ããŠVIAãšã®å
±åãäžå¯ã«ãªãã
ãŸãããŒè¡šç€ºå
容ãåæ§ã工倫ã®äœå°ããã
ã»0x5DADãæŒããŠã®ã¹ã¯ããŒã«
ã»Layer3ã«ç§»è¡ããŠã®ã¹ã¯ããŒã«
ã©ã¡ãã®å Žåã§ãã埩垰åŸäžã¯ãªãã¯(MouseBtn3)ã®ïŒã¯ãªãã¯ç®ãåå¿ããªã
ïŒã¯ãªãã¯ç®ä»¥éã¯åå¿ããã
åèïŒ
埩垰åŸã«MouseBtn1,2ãã¯ãªãã¯ãããããŠãå€ãããã
MouseBtn3ã¯2åç®ä»¥éã®ã¯ãªãã¯ããåå¿ããªã
ç§ã®ç°å¢ã ãã§ãããç³ãèš³ãªãã®ã§ããããå ±åãŸã§ã«ã
come from #81
There are less documents about frimware development.
çªç¶ãã¿ãŸãããå
æ¥keyball61ãéèå·¥æ¿ã«ãŠè³Œå
¥ãããã©ãã¯ããŒã«ICãå£ããŠããŸã£ãããshirogane labãã賌å
¥ãããŠããã ãããã®ã§ããå±ããã®ã§åãä»ãããšãããåçã«ããéã4ã€ã®ããŒãåå¿ããªããªã£ãŠããŸããŸããããã©ãã¯ããŒã«åºç€ãæãåãŸã§ã¯ã¡ãããšäœ¿ããŠããŸããã解決ããæ¹æ³ãããããªãã®ã§æããŠããã ãããšå¹žãã§ãã
Keyball61, without the ball, left side.
when pressing v
and a
, ]
is pressed unexpectedly.
Original report: https://twitter.com/jomatsu_/status/1514968357841543168
èªåã®keyball61ã¯vãšaãåææŒããããš[ãå ¥åãããŠããŸããŸãã
(He maps [
at ]
's default position)
DããŒãåå¿ããŸãããäœåºŠãçç¶ãåçºããŠããããã®åºŠã«ã¯ãã ãçããšè§£æ±ºããŸããããä»åã¯è§£æ±ºããå
ãããããŸããã
åã¯ããŒã匷ãæŒããšèªèãããŸããããä»åã¯èªèããã
ãã³ã§å°é確èªåŸã¯èªèãããããã«ãªãããšãã£ãè¬ãå€ãäžå ·åãçºçããŠããŸããã©ããããæ²»ãã§ããããïŒèãããåå ãæ¹åçããããŸããããæ瀺é ãããã§ãã
it will be failed that compile with MOUSEKEY_ENABLE = yes
in rules.mk
çŸåšãããã«ãã©ãã¯ããŒã«æ§æã§ã¯USBãç¹ãã åŽããã€ã³ã¿ã
ç¹ãã§ããªãåŽãã¹ã¯ããŒã«ãšãªã£ãŠããŸãã
ãããconfig.hã§å·Šå³ã«ããåºå®ã§ããããã«ããŸãã
ãã ãdual ballã§äœ¿ã£ãŠã人ã¯ã»ãŒããªãã®ã§åŸåãã
When you use Keyball with double ball combination,
a ball on USB connected side is treated as mouse move.
And other side ball is scroll wheel.
We make it configurable by config.h or so: depending right or left.
But this is low priority because there are few peoples who use double ball.
Hi I bought the keyball. I tried to compile the firmware and it fails on the latest QMK.
è³Œå ¥ãããããã§ã¯ããŒã«èªã¿åãåºæ¿ãçµã¿ç«ãŠæžã¿ã§ããã
ãã®ãã ãã®æé ã«å°éããéã«è¥å¹²å°æããŸããã
ã²ãšããšèšåããããšå©ãããŸãã
å
æ¥ãéèå·¥æ¿ã§keyball39ã賌å
¥ããå¶äœããŸããããããŒã®åäœã確èªãããšãããïŒã€ã®ããŒãé€ãå
šãŠã®ããŒãåå¿ããŸããã§ããã
åç°ä»ããå®å
šãã¯ããããŸããããå·¥æ¿ã®æ¹ã«é»æ°ãéãã確èªããŠããã ãããšãããéã£ãŠãããšã®ããšã§ãããã®ç¶æ
ã§ã»ãšãã©ã®ããŒãåå¿ããªããšãªããšããã®æ¹ã ãšåå ãç¹å®ã§ãããããããªãã®ã§ããã¡ãã§çžè«ããæ¹ãè¯ããšãææ¡ããã ããé£çµ¡å·®ãäžããŸããã
以éã®å¯ŸåŠã«ã€ããŠãæ瀺ãé ããã°å¹žãã§ãããããããé¡ãããŸãã
https://twitter.com/kaspinMTH/status/1487649434263785472
windows 10 proã䜿çšããŠããã®ã§ãããã¹ãªãŒãã¢ãŒããã埩垰ããéãkeyball46ãèªèããŸãããOLEDã«keyballã®ããŽã衚瀺ãããç¶æ ã«ãªããŸãã TRRSã±ãŒãã«ãæãå·®ããããèªèããŸãã
ã©ãããã°ã¹ãªãŒã埩垰ããæç¹ã§keyball46ãèªèããŸããïŒ
QMKç±æ¥ã®åé¡ããKeyballãšã®åããæã®åé¡ãããŸããã®åãåããå¿ èŠã
Since this has been out of stock for such a long time, I am looking at printing everything myself. I assume the trackball PCB in keyball46 is universal. But, it seems like there is no 3D printer files for the trackball mount.
Am I missing something?
åçãªãªãŒã¹åŸã«åããŠã®issueã§ãã
VIA+ãã©ãã¯ããŒã«ãã©ã€ã+ãã«RGBLIGHTã§ã¯å®¹éããªãŒããŒããŠããŸããŸããŸãã
ãããäœãšãã§ããªããæ€èšãããã§ãã
Hello,
Thanks for the great projects.
by the way I hope you guys translate Japaneses to English.
Cause I want a build keyball 46.
ãã«ãã¬ã€ãã®æåã«ç®æ¬¡ã欲ããã§ãã
äžå¯§ã«æžãããŠå·¥çšæ°ãå€ãã®ã§å
šäœãæŠèŠ³ããæå³ãšã
äœæ¥äžæåéæã«å¿
èŠãªé
ç®ãçŽ æ©ãåç
§ã§ããããã«ããæå³ã§ã
ãã«ãã¬ã€ãã®å
é éšåã«ã€ã³ããã¯ã¹ããããšããã«äŸ¿å©ã«ãªãããã§ãã
http://www.neko.ne.jp/~freewing/hardware/qmk_update_program_with_newest_firmware_2022/
As I found something like this article happen, and in the end, this gives such a error:
âŠ\qmk_firmware/keyboards/keyball/lib/keyball/keyball.c:499: undefined reference to `register_button'
| collect2.exe: error: ld returned 1 exit status
|
make[1]: *** [builddefs/common_rules.mk:267: .build/keyball_keyball44_default.elf] ãšã©ãŒ 1
Make finished with errors
make: *** [Makefile:414: keyball/keyball44:default] ãšã©ãŒ 1
`register_button' is not defined.
How this suppose to work? And how can it be fixed?
æ¯åæžããã(=ã³ããŒãã)ã®ã¯ã¢ããããã®ã§
trackball.c ãšåæ§ã«å¯èœãªéãå
±ééšåãšããŠãããåºããããšèããŠããŸãã
C(KC_BTN1)
doesn't work.
Because, Keyball firmware implements own minimal MOUSE key feature for size.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
ð Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ððð
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google â€ïž Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.