tankplanker @ tankplanker @lemmy.world

Posts

5

Comments

686

Joined

2 yr. ago

Thats the cool thing about 40s, there is so much more variety with layouts compared to larger boards that you are bound to find something that you like

The interval is configurable, so you can allow as much or as little time as you like. Shorter tends to be better for keys that you would press one after like r and e so you don't trigger the chord for works like read, really, and so on. Chords like qw you could have as long as you want.

Nice, it does look a fun project though!

I copy and paste anything that's missing, Wikipedia has a nice key code page.

But seriously, it's on a chord for p and ;, I press both and that's backspace. ; and " are delete.

Chords are game-changing on smaller boards, particularly 30%. That and moving the mod keys (control etc.) to the home row (and row).

From scratch? Or a kit?

I've never tried a wireless keyboard (despiteowningmore than 50), still waiting on my Pearl three years after I ordered it lol, that would have been my first.

All my splits are cabled, so it's no issue for me.

Another option is home row layer keys, duplicating the layer options in pairs so a and h, s and j, and so on so you have the same layer from each side.

Smaller boards I use home row mods (control, super, and so on), and that works extremely well for me.

I prefer zwave and zigbee because they give me 12 months plus on small batteries, and I can not get this on WiFi devices. This greatly improves where I can install sensors and the like.

Even when I have a larger battery, such as the 60ah battery I use for my back garden lighting, I still use them as it reduces power draw over a WiFi controller.

I can also directly connect them to smartthings and more recently home assistant thst I have migrated to rather than connecting to a WiFi device via a Web service. This improves reliability and speed on average.

I get no problems with running a large network of such devices, I have over 100 bulbs, relays, plugs, and sensors that are connected. My WiFi is decent and supports 8 nest cams that are outside plus another 20 or so devices that are inside, so it offers a similar range for me.

Thank you!

It's an equinox xl that I built with switches I don't even remember what the recipe I used for them as I prepared them early last year other than they are zealio stems and top housing that are lubed and filmed. I do remember that I wanted the longer stem in a shorter housing.

I had a very long wait for it, more than 8 months after the rest of the world got theirs.

ZMK also has a layer tap key that would suit for this, normal key press of your choosing and layer activation while holding: https://zmk.dev/docs/keymaps/behaviors

I have a large selection, but I rarely use them for anything other than media keys and teams call functions. Other stuff like windows management in sway are all done on higher layers on my (40%) keyboard.

My preference is for something with at least one knob as knobs are my preference for things like scrolling, volume control, and zoom.

If you can find latching switches, these are great for triggering layers so you can get more out of your pad. You can obviously do latching layer changes without such switches in QMK, but you really need to trigger leds to help you remember which layer you on otherwise.

Pad I use the most is a CapsUnlocked CU7 that I got just before they imploded as I love the weight of the knob.

Do you mean keys thst you hold down with your thumb while your fingers are on the home row or something else? For the former, I use split space keyboards and map the left one to enter on press, layer on hold, the right one to space on press, and a different layer on hold. That gives me more keys that you would get on a 70+ keyboard. I find this considerably easier than trying to use pinkies on shift and symbols on what is my top row, qwerty row.

Typically, I map tab and the traditional enter key to tab on press, another layer, and backspace with the same layer as tab. This layer I use for window management in sway for home row and anything else I am missing that I really want.

Cant help feel this will be like the later seasons of Witcher were they wanted a big name to give them a built in audience to their own stories rather than actually adapting what is there. This rarely works as fans of the books want the book adapted not something new and different badged as coming from the book.

Second problem is that Neuromancer was very much of its time, much of its concepts have become standard tropes now across the genre and even in everyday life. This greatly limits its impact to audiences new to Neuromancer as they have seen it all before.

I will give it a go but I am not holding out much hope.

The keyboard has me interested as I cannot stand modern laptop keyboards being a big mechanical keyboard fan.

I would hope that they would do the option to solder your own switches as I am not the biggest fan of the browns plus I would really want to lube my switches.

They seem to make the PCB opensource so I guess I could just get a PCB printed and do it myself but its extra expense. However I would be very tempted to redesign the layout as I really do not like that layout at all as it has way too many keys for me to be useful. I also prefer 3u/1u/3u for my space-bar setup.

As its using v2 chocs it should take DSA MX stem keycaps without it fouling the screen but I would like that confirmed from them. As I already have a ton of 40% keyboards I have a number of DSA sets that would fit as those sizes are pretty standard for "normal" mechanical keyboards.You would lose the shine thru but I see that as a bonus

Final thing, it would have been nice if it was running QMK via VIAL for the keyboard, would make it easy for me to port my standard map to it. However I do like that you can configure the keyboard directly, always prefer that to having to remap in Linux.

Yeah its not going to mm perfect, but then its still going to be far better than just doing the static load test that is clearly inadequate to settle the issue beyond reasonable doubt when the wings are clearly flexing on camera.

By putting a calibrated ruled mark set on camera you will be able to measure the max deflection with a level of accuracy. Setting a upper and lower limit, then if its a clear breach the wing has to be changed I think is fair. If its just about on the line then it not going to be mm perfect for a ruling but should be enough to trigger more investigations.

VAR in the Prem is fucking useless, its not much more than an old man squinting at various TV angles. VAR elsewhere uses SAOT system that should be coming to the Prem later.

Another ineffective clampdown? The static load tests never satisfy the accuser or the accused, how many times have we seen a wing flexing on an onboard yet it passed some new and improved test? Would be far easier if it was measured by deflection on the car using FIA measured points during the race via cameras.

Low T also causes hairloss...

Also, I used the difficulty in getting TRT when HRT is so widely available as a perfect example of how much harder it is to get medication for men from the NHS.

It wasn't just releasing licensing for that film, it was permanently releasing licensing similarto Winnie teh Pooh. They would have lost control completely.

Its availability of treatment as well for mens health. TRT thresholds that the NHS applies to men are insanely low, almost like they do not want to spend the money rather than provide actual benefit to people with low test. Its pretty bad as the threshold for women to get HRT is almost non existent and its just given out without further tests.

While I think TRT should only be issued once tested it should be at higher thresholds as it solves so many other issues. However like the new weight loss drugs we do not give the NHS enough money to stick it on prescription for everybody that would benefit from it, particularly as both are likely to be very long term to whole life treatments.

Mine is probably more of a combo of things to streamline my workflow than anything else.

I use Sways multiple workspaces to segregate my apps into different workspaces for different tasks on startup of that app using the assign function in my Sway config. For example VS Code and one particular Firefox window always goes to Workspace 3.

I use the Layman Sway scripts to force all my normal workspaces to different layouts that is appropriate for that function. So workspace 3 with VS Code and a Firefox window is set in a 75/25 split with VS Code set to always take the bigger share. I can switch the two sides from largest on the left to largest on the right, or swap the apps between the two splits, or make a window full-screen with simple keyboard shortcuts.

Odd workspaces are on my left monitor, even ones on the right. This coupled with per workspace wall paper (all my windows are translucent, not for everybody I know) and particular tasks locked to predefined workspaces means I am never hunting around for something. Even if I did lose something I can use rofi to switch to it. If its an essential app I can use my keyboard shortcut that I use to launch the app, switch to it using swayr by activating the shortcut again.

I have used QMK for my keyboard to reduce the number of keys I must use to activate most of my shortcuts, and move them to my number row and home row using layers, double taps, and holds. I try to layer up the same family of functions on the same key but on different layers, so for example, the VI arrow keys move between windows, resize windows, move windows, depending on which layer I have chosen.

Sway (and i3) you can assign windows to workspaces based on any property that is available in the swaymsg tree. It can do parital matches, so for example if you wanted your Lemmy firefox window to always start on workspace 3 you could use:

assign [title="lemmy" app_id="firefox"] workspace number $ws3

Title can use regex so you can do some pretty neat matching if you need it.

I do something similar.

I have a V4N4G0N that I use the top row (half the normal number row on a full sized board) for switching workspace or switching apps to another workspace, and doing other stuff like copy and paste on different layers for the keyboard.

As its QMK (via VIAL) I have set all that up directly on the keyboard so its portable to any other PC I want to use. I have eight of these, mix of alu, acrylic and 3D printed, that I can choose from, all sharing the same map. I don't like using anything else now as its become integral to my normal workflow.