I don’t think they’re saying it failed. They’re saying that it will fail long before the body ever does.

Keep an eye on them, they drop new stuff semi-regularly. It’s all handmade so not constantly fully stocked.

https://www.asymplex.xyz/

Ergos can be actually relatively cheap. That’s why I’ve spent god-knows how much and have like 30 of them.

It’s a nonsensical statement to us programmers too.

I’m pretty sure that’s a claw44

Does your keyboard have asymmetric halves? The left having 7 columns and the right having 6? As the other commenter pointed out you have defined 6 columns but your layout macro in eiris.h has 7 elements for the left hand. I think the way to solve it is to define it as 7 columns, add NO_PIN to the end of MATRIX_COL_PINS_RIGHT and then just add XXX to the end of all the rows for the right half in your layout macro in eiris.h.

This is outlined in the documentation

You might want to have a browse of !ergomechkeyboards@lemmy.world as well as the subreddit. Within that budget the best bet is likely something DIY. Though there is a middle ground with vendors offering build services and kits that are hot-swappable, turning “building” into “assembling”.

Have a look at some popular choices and lists likes in the EMK wiki that I put together.

A lot of people seem to not understand what a fallacy is. They think that if something is fallacious then it is necessarily false, which ironically is a fallacy in and of itself (the fallacy fallacy). All that a fallacy is is an argument that does not logically follow from the starting axioms and the conclusion. Slippery slopes are predictions, sometimes accurate ones, but it does not necessarily follow that some of a thing leads to more of that thing, thus it is a fallacy.

Generally yes, for keyboards without a number row we will tend to use some combination of those kinds of tricks. In the past I’ve had numbers on the homerow under an fn key (note that said fn key is on a thumb key so easier to press than the standard location for fn keys on regular keyboards). Currently I have a number row as vertical combos on my Sweep (34 key low profile split). So q+a = 1, w+s = 2, and so on. As well as a numpad on one half under a fn key (we call these layers). So for long strings of numbers I use the numpad layer, for short ones I use my “virtual number row”.

However, I got here gradually, my first split was a keebio Iris (which has a number row) and have gone progressively in the direction of smaller ones. There are a good number of numrow inclusive splits out there. Some examples:

• ergodox
• moonlander
• dygma raise
• Lily58
• Sofle
• Iris

Splitkb.com is due to release the Elora (Kyria, but with a number row) Any Day Now™️

On foot pedals, I have a stack of them but haven’t got around to making use of them in any projects yet. Others have

Most of the time it’s not exactly useful and some of the positions are awkward (e.g. 8, 9, 10), counting to 31 on one hand is maybe useful.

More useful IMO is counting in base 6 and treating each hand as a single digit. i.e counting to 35 on 2 hands without awkward fingerings. Better than 10, less awkward than binary.

Even with AI models that can identify that there are birds in the picture. Having it decide with accuracy that the picture is of a bird is still a hard problem.

I agree, I’m just answering the why question. Free software licenses don’t have non-commercial clauses and they want an NC clause.

I presume the reason they didn’t use GPL3 is because they wanted the attribution and non-commercial clauses offered by CC-BY-NC.

Not suggesting that they should not prefer to drop those clauses in favour of a copyleft free software licence. but you asked “why not” and losing those clauses is clearly an obvious candidate for why they might not want to.

Ideally you want to use QMK’s tri_layer feature as I outlined in this comment.

Also you can just use the _______ keycode instead of restating MO(...) on every layer as that is the an alias for KC_TRANSPARENT meaning it maintains the function of the layer below.

This doesn’t work perfectly, IIRC if OP presses MO(1), then MO(2), then releases MO(1) it’ll stay on layer 3. The better way to do it is defining the layer_state_set_user function and calling update_tri_layer_state as documented here

Ricardo was testing in production

I didn’t notice that 7,8,9 had no effect on the count. My bad.

I know this doesn’t answer the question but I want to offer some advice instead.

In my opinion just don’t. If the company want you to have access to emails on the go then they should give you a company phone. If they don’t, why are you trying to? Don’t put work things on your personal phone.

Chars are just numbers, but yeah, an enum would work fine too, sure. The only advantage with using a char for it is that there’s no conversion needed for outputting them into strings so it’s a little easier. Less code, very readable, etc. Though yeah, thinking about it JQKA wouldn’t be numerically in the right order which could cause issues if the program did more than just implement HiLo