Adjusting times in mod rows

Dear all.
I’m experimenting with mod rows (bottom in my case, since with my Spanish Dvorak the middle row has too many collisions with common pairs) and I´m really liking it very much. :slight_smile:

The only issue I’m encountering is that sometimes a tap -when the letter is the desired result- it gets registered as a mod, a clearly unwanted result (and using emacs it could even be dangerous) :laughing:

The current hypothesis is that this happens because the separation between both keys is too short (ie, the typing speed is relatively high).

I tried to adjust the time sensitivity in Chrysalis, but couldn’t find that setting there.
Does it needs to be tweaked from other place?

I poked quite much from Chrysalis, but never touched anything else and I’m afraid it could be too complicated for me.

As always, thank you very much for sharing your time, knowledge and attention.
Warm regards… :smiley:

@algernon ? Please? :grinning_cat_with_smiling_eyes:

I’m also interested in this, although my Model 100 is still in transit. From what I’ve read so far, it seems Kaleidoscope may be the tool required for this level of fine-tuning, but I’ll wait for the experts to weigh in :grinning_face:

Hi Frank!

Thanks a lot for your touch. :slight_smile:
It seems we will have to check that out.
I’d love to start from what I currently have (since I’m quite happy with it). I assume that there is a way to dump the current state and tweak from there, right? :hopeful: :slight_smile:

Best…

Hi Eduardo,
As I mentioned, my Model 100 hasn’t arrived yet, but I’ve been using a couple of Atreus boards and a 3w6 with QMK for a couple of years, with the Miryoku layout. I found Home Row Mods very convenient to use, especially for the shift modifier. I’ve recently moved to Bottom Row Mods because the odd Ctrl-Q misfire broke my flow too badly and I’m slowly adapting.
It seems Kaleidoscope has the functionality we’re looking for: Qukeys — Kaleidoscope documentation. I may need to become more familiar with Kaleidoscope, but I’ll try to adapt to the board first, then determine what changes to make. I also use Emacs, btw.

[…] I’ve been using a couple of Atreus boards and a 3w6 with QMK for a couple of years, with the Miryoku layout.

I very recently noticed it and it seems quite solid and coherent. Of course, it doesn’t mean it works the same for everyone, but I’m seriously looking at it.

I found Home Row Mods very convenient to use, especially for the shift modifier. I’ve recently moved to Bottom Row Mods because the odd Ctrl-Q misfire broke my flow too badly and I’m slowly adapting.

Something similar here, home row mods doesn’t work well with Dvorak (my layout, Spanish version) because the home row is by far the most used. Also, since it’s design maximizes alternates hands, it is terrible frequent to get mods instead of the desired keys. But the bottom row is the least used in Dvorak, so perfect for a mod row. :wink:

It seems Kaleidoscope has the functionality we’re looking for: Qukeys — Kaleidoscope documentation. I may need to become more familiar with Kaleidoscope, but I’ll try to adapt to the board first, then determine what changes to make.

Seems logical. I will start looking at how to work with Kaleidoscope, thanks a lot for the pointer. :slight_smile:

I also use Emacs, btw.

Great! :smiley: Maybe at some point the Emacs/M100 users can have a meeting … :stuck_out_tongue_winking_eye:

Best!

Seconded (again). Home row mods did not work for me with another optimized layout I run (RSTHD), and like you I put them in the lower row. Maybe those who fetishize ultimate ergonomics over something that is actually usable would disagree, and perhaps it works better on QWERTY, but I found the lower row mods an ideal compromise.

Hi David!

While ergonomics have a common, shared base (human anatomy and cognition) there are also many individual and contextual factors: languages and their characters, frequent expressions, individual preferences, size of hands, different flexibility in different fingers, etc.. :wink:

So there are no absolute ultimate ergonomics that anyone can claim as universally valid for everyone in every case. What works better for us is the best for each one of us. :smiley:

I still have the arduino open here, but I recognize that I’m afraid :fearful: of borking something and loosing many hours of using my loved M100 to work and enjoy…

Whilst what you say is undoubtably true, there is a point where these “optimizations” are into diminishing returns. There is a difference between gaming a computer-generated score for the most ergonomic possible layout and what is actually usable on a daily basis, especially when you booby-trap your layout with ill-considered tap-mod keys.

And whilst I like “RSTHD”, complete with “E” on the thumb key, we can get a bit carried away on the benefits of these novel layouts - or the perceived handicap of traditional staggered row format and QWERTY. Consider that almost every book you read will have been hammered out on QWERTY, unless it is a “classic” that was written by hand with ink.